Skip to main content
Mallory
HighVulnerability

CVE-2026-120145: Arbitrary Code Execution in PostgreSQL Logical Replication

Published Nov 12, 2026 · Updated today
Trending this week#86of 428,812 vulnerabilities
Mention activity · 30 days18 mentions · peak 6 in a dayToday
CVSS8.8High · v3.1
EPSS0.54%46th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-120145CWE-862 · Missing Authorization

CVE-2026-120145 is a missing-authorization vulnerability in PostgreSQL logical replication. A compromised publisher can name a system catalog as a replication target, causing replication to write to subscriber system catalogs and enabling arbitrary code execution on the subscriber. Code executes as the operating system user running the subscription. Only subscriptions owned by a PostgreSQL superuser are vulnerable. Affected releases are PostgreSQL 18.x before 18.7, 17.x before 17.12, 16.x before 16.16, 15.x before 15.20, and 14.x before 14.25.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the subscriber under the operating system account running the subscription, potentially allowing access to sensitive database data, unauthorized modification of database contents and system catalogs, and disruption of database services. The resulting access is bounded by that operating system account's permissions; operating system root privileges are not established.

Mitigation

If you can’t patch tonight, do this now.

No vendor-specified workaround is documented. Subscriptions not owned by a PostgreSQL superuser are not vulnerable to this issue.

Remediation

Patch, then assume compromise.

Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later maintenance release within the applicable branch. The fix rejects system catalogs as logical replication targets. Distribution-managed installations should apply the corresponding vendor security update. PostgreSQL 14.25 is the final release of that branch, so PostgreSQL 14 deployments should also plan migration to a supported major version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-120145 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-120145 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-120145?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-120145.
Is there a patch for CVE-2026-120145?
Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later maintenance release within the applicable branch. The fix rejects system catalogs as logical replication targets.
How severe is CVE-2026-120145?
CVE-2026-120145 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.54% (46th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
krcert kisaNews · Nov 17, 2026PostgreSQL 제품 보안 업데이트 권고 > 보안공지 > 알림마당 : KISA 보호나라&KrCERT/CCMissing authorization vulnerability in PostgreSQL. The advisory recommends updating affected branches to 18.7, 17.12, 16.16, 15.20, or 14.25 or later within the corresponding branch.Read more ↗tenable nessus pluginsNews · Nov 15, 2026Rocky Linux 9.6 [TuxCare] Security Update: postgresql / postgr... | Tenable®Provides the check's CVSS v2 vector, indicating network exploitation with low complexity, no authentication, and complete confidentiality, integrity, and availability impacts. The underlying flaw and affected package are not described.Read more ↗tenable nessus pluginsNews · Nov 15, 2026AlmaLinux 9.6 [TuxCare] Security Update: postgresql / postgres... | Tenable®Referenced as the CVSS v2 score source for the AlmaLinux 9.6 security check. The supplied vector indicates network exploitation with low complexity, no authentication, and complete confidentiality, integrity, and availability impacts. The underlying flaw and affected package are not described.Read more ↗tenable nessus pluginsNews · Nov 15, 2026AlmaLinux 9.2 [TuxCare] Security Update: postgresql / postgres... | Tenable®Referenced by an AlmaLinux 9.2 security-update check and used as its CVSS v2 score source. The supplied vector describes network exploitation with low complexity, no authentication, and complete confidentiality, integrity, and availability impacts. The underlying flaw and affected component are not described.Read more ↗
+8 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.