cve.bz

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

8.8 highEPSS 0.5%

High (8.8). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
PostgreSQL (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-120145 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120145?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120145?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120145 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-120145

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-120145](https://cve.bz/cve/badge/CVE-2026-120145.svg)](https://cve.bz/cve/CVE-2026-120145)

HTML:

<a href="https://cve.bz/cve/CVE-2026-120145"><img src="https://cve.bz/cve/badge/CVE-2026-120145.svg" alt="CVE-2026-120145"></a>

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12postgresql-15no fix listedDEBIAN-CVE-2026-120145
Debian13postgresql-1717.12-0+deb13u1DEBIAN-CVE-2026-120145
Debian14postgresql-18no fix listedDEBIAN-CVE-2026-120145
Ubuntu20.04:LTSpostgresql-12no fix listedUBUNTU-CVE-2026-120145
Ubuntu22.04:LTSpostgresql-14no fix listedUBUNTU-CVE-2026-120145
Ubuntu24.04:LTSpostgresql-16no fix listedUBUNTU-CVE-2026-120145
Ubuntu26.04:LTS, 26.10postgresql-18no fix listedUBUNTU-CVE-2026-120145
UbuntuPro:14.04:LTSpostgresql-9.3no fix listedUBUNTU-CVE-2026-120145
UbuntuPro:16.04:LTSpostgresql-9.5no fix listedUBUNTU-CVE-2026-120145
UbuntuPro:18.04:LTSpostgresql-10no fix listedUBUNTU-CVE-2026-120145
Red Hathummingbird:1libpq, libpq-devel0:18.7-0.1.hum1RHSA-2026:99821
Alpinev3.21, v3.22postgresql1515.20-r0ALPINE-CVE-2026-120145
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1616.16-r0ALPINE-CVE-2026-120145
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1717.12-r0ALPINE-CVE-2026-120145
Alpinev3.23, v3.24postgresql1818.7-r0ALPINE-CVE-2026-120145
Azure Linux3postgresqlno fix listedAZL-113759

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat rates this vulnerability as Important because an attacker controlling an upstream publisher can achieve arbitrary remote code execution under the postgres operating system user account on the subscriber host. In default Red Hat Enterprise Linux installations, PostgreSQL does not establish logical replication subscriptions out of the box, significantly limiting ambient exposure. The security risk is restricted to specific environments where an administrator has configured a superuser-owned subscription that pulls changes from an untrusted or compromised external database instance.

Red Hat's mitigation

Disable logical replication subscriptions connected to untrusted publisher databases, or reassign subscription ownership to an unprivileged database role.

1. Disable an untrusted subscription directly from the PostgreSQL prompt:

ALTER SUBSCRIPTION <subscription_name> DISABLE;

2. Alternatively, transfer the subscription ownership away from a superuser:

ALTER SUBSCRIPTION <subscription_name> OWNER TO <non_superuser_role>;

3. Restrict outgoing network connections to unverified publisher hosts at the network or firewall level.

Caveats: Disabling subscriptions halts data synchronization between publisher and subscriber tables until manually re-enabled. Non-superuser roles must have adequate table privileges to apply replicated data.

Warning: Modifying subscriptions or applying firewall changes interrupts active replication sessions but does not require a PostgreSQL service restart.

ProductPackageStateAdvisory
Red Hat Hardened ImageslibpqAffected
Red Hat Hardened Imagespostgresql17Affected
Red Hat Hardened Imagespostgresql18Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-120145.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON