# CVE-2026-120153: PostgreSQL extension-script substitutions allow SQL injection through object names

> 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.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** ALPINE-CVE-2026-120153, DEBIAN-CVE-2026-120153, ECHO-038e-d30b-d299, GHSA-w429-xmhm-p6jc

## What is CVE-2026-120153?

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.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-120153?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-120153?

Upgrade to a fixed version.

## Is CVE-2026-120153 being exploited?

There is no known exploitation of CVE-2026-120153 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120153 and fix it if it is affected.

What 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.
Exploitation: 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.

Affected product: PostgreSQL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120153/ (Markdown: https://insights.sbomify.com/CVE-2026-120153/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120153
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120153
- OSV: https://osv.dev/vulnerability/CVE-2026-120153

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120153/
Summaries are generated and may contain mistakes; the official description above is the record.