{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120151 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"Upgrade to a fixed version.","what":"CVE-2026-120151 is a high-severity memory corruption vulnerability in PostgreSQL, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-120151 and fix it if it is affected.\n\nWhat it is: CVE-2026-120151 is a high-severity memory corruption vulnerability in PostgreSQL, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-120151 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: PostgreSQL. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-120151/ (Markdown: https://insights.sbomify.com/CVE-2026-120151/index.md)","id":"CVE-2026-120151","markdown":"https://insights.sbomify.com/CVE-2026-120151/index.md","name":"CVE-2026-120151","record":{"aliases":["ALPINE-CVE-2026-120151","DEBIAN-CVE-2026-120151","ECHO-99c4-e805-1871","GHSA-92mx-px77-82fx"],"analysis":{"component_type":"database","exploitable_when_present":false,"fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"relational database","requires_auth":"low_privilege","requires_specific_call":false,"summary":"An object creator can execute code as the database OS user via type confusion in PostgreSQL plpgsql record-field assignment.","user_interaction":"not_required","vuln_class":"memory_corruption","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"PostgreSQL","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"Type confusion in PostgreSQL plpgsql record-field assignment allows an object creator to execute arbitrary code as the operating system user running the database, via a reentrant domain CHECK that changes a RECORD variable's row type while a value is being cast.  Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"PostgreSQL plpgsql record-field type confusion executes arbitrary code","id":"CVE-2026-120151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PostgreSQL pg_show_all_settings() use-after-free discloses memory","id":"CVE-2026-120152"},"nickname":null,"packages":[],"prev":{"headline":"PostgreSQL expanded-record domain-check use-after-free executes arbitrary code","id":"CVE-2026-120150"},"products":["PostgreSQL"],"published":"2026-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-12","vendors":["n/a"]},"summary":"An object creator can execute code as the database OS user via type confusion in PostgreSQL plpgsql record-field assignment.","url":"https://insights.sbomify.com/CVE-2026-120151/"}