{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120153 in the wild and no public exploit code.","exposure":"Only installations with a non-default setting turned on are exposed.","fix":"Upgrade to a fixed version.","what":"CVE-2026-120153 is a high-severity SQL injection vulnerability in PostgreSQL, published on 12 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-120153 and fix it if it is affected.\n\nWhat it is: CVE-2026-120153 is a high-severity SQL injection vulnerability in PostgreSQL, published on 12 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-120153 in the wild and no public exploit code.\nExposure: Only installations with a non-default setting turned on are exposed.\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-120153/ (Markdown: https://insights.sbomify.com/CVE-2026-120153/index.md)","id":"CVE-2026-120153","markdown":"https://insights.sbomify.com/CVE-2026-120153/index.md","name":"CVE-2026-120153","record":{"aliases":["ALPINE-CVE-2026-120153","DEBIAN-CVE-2026-120153","ECHO-038e-d30b-d299","GHSA-w429-xmhm-p6jc"],"analysis":{"component_type":"database","exploitable_when_present":false,"fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"relational database","requires_auth":"high_privilege","requires_specific_call":false,"summary":"A database user with CREATE privilege can inject SQL via object names to run code as the bootstrap superuser on PostgreSQL with vulnerable extension scripts.","user_interaction":"not_required","vuln_class":"sql_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"PostgreSQL","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection in PostgreSQL extension-script substitutions allows an attacker with database-level CREATE privilege to execute arbitrary code as the bootstrap superuser, via a schema or owner name containing newlines or other special substrings.  This is similar to CVE-2023-39417, but it requires a non-bundled extension with a vulnerable script pattern.  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 extension-script substitutions allow SQL injection through object names","id":"CVE-2026-120153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PostgreSQL INSERT ... ON CONFLICT can read rows despite row security policies","id":"CVE-2026-120154"},"nickname":null,"packages":[],"prev":{"headline":"PostgreSQL pg_show_all_settings() use-after-free discloses memory","id":"CVE-2026-120152"},"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":"A database user with CREATE privilege can inject SQL via object names to run code as the bootstrap superuser on PostgreSQL with vulnerable extension scripts.","url":"https://insights.sbomify.com/CVE-2026-120153/"}