# CVE-2026-120145: PostgreSQL logical replication can write to subscriber system catalogs, executing arbitrary code

> A compromised PostgreSQL publisher can name a system catalog as a replication target to run code as the superuser's subscription user.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **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-120145, DEBIAN-CVE-2026-120145, ECHO-24a8-ca62-a008, GHSA-j3p3-grqw-h5vf

## What is CVE-2026-120145?

CVE-2026-120145 is a high-severity missing authorization vulnerability in PostgreSQL, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Missing authorization in PostgreSQL logical replication allows a compromised publisher to execute arbitrary code as the operating system user running the superuser-owned subscription, via naming a system catalog as a replication target.  Only subscriptions owned by a superuser are vulnerable.  Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Weakness: CWE-862 (Missing Authorization)

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-120145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120145 is a high-severity missing authorization vulnerability in PostgreSQL, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-120145 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-120145/ (Markdown: https://insights.sbomify.com/CVE-2026-120145/index.md)
```

## Sources

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

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