Skip to main content
Mallory
HighVulnerability

CVE-2026-120150: PostgreSQL Expanded-Record Domain-Check Use-After-Free Code Execution

Published Nov 12, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days16 mentions · peak 5 in a dayToday
CVSS8.8High · v3.1
EPSS0.58%48th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-120150CWE-416 · Use After Free

CVE-2026-120150 is a use-after-free vulnerability in PostgreSQL expanded-record domain-constraint checking. Repeated checks of a domain over a composite type can reuse a dangling memory-context pointer, allowing a database object creator to execute arbitrary code as the operating system user running PostgreSQL. Affected releases are PostgreSQL 18 before 18.7, 17 before 17.12, 16 before 16.16, 15 before 15.20, and 14 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 confidentiality, integrity, and availability through arbitrary code execution under the PostgreSQL operating system account. An attacker can potentially access or modify database data and other resources accessible to that account, or disrupt database service. This does not inherently grant operating system root privileges.

Mitigation

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

As an interim risk-reduction measure, restrict database object-creation privileges to trusted roles. This addresses the stated attacker prerequisite but is not a confirmed substitute for upgrading; no vulnerability-specific workaround is established.

Remediation

Patch, then assume compromise.

Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later maintenance release in the applicable branch. Debian 12 PostgreSQL 15 packages are fixed in version 15.20-0+deb12u1. For upstream minor-version updates, stop PostgreSQL, update the binaries, and restart the service; a database dump/reload or pg_upgrade is not required. PostgreSQL 14.25 is the final release of that branch, so deployments should migrate 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-120150 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-120150 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-120150?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-120150.
Is there a patch for CVE-2026-120150?
Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later maintenance release in the applicable branch. Debian 12 PostgreSQL 15 packages are fixed in version 15.20-0+deb12u1.
How severe is CVE-2026-120150?
CVE-2026-120150 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.58% (48th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

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

View more in app →
+7 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.