CVE-2026-120139: PostgreSQL Tuple-Size Integer Wraparound Code Execution
CVE-2026-120139 is an integer wraparound vulnerability in PostgreSQL's in-memory tuple-size calculations. A database user can supply oversized tuple data to trigger the flaw and execute arbitrary code with the privileges of the operating system account running PostgreSQL. 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.
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 PostgreSQL server process and permits arbitrary code execution as the database service's operating system account. This can expose or allow modification of data and other resources accessible to that account and disrupt database availability. The vulnerability has a CVSS v3.1 score of 8.8, with high confidentiality, integrity, and availability impacts.
Mitigation
If you can’t patch tonight, do this now.
No vulnerability-specific workaround is identified. Until patched, restrict database connectivity and database account access to trusted users. Network restrictions alone do not prevent exploitation by an existing authorized database user.
Remediation
Patch, then assume compromise.
Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later fixed release in the corresponding branch. Debian 12 PostgreSQL 15 installations can apply package version 15.20-0+deb12u1 or later. PostgreSQL 14.25 is the final release of its branch; migrate PostgreSQL 14 installations to a supported major version for continued security updates.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-120139 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-120139 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-120139?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-120139.
- Is there a patch for CVE-2026-120139?
- Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later fixed release in the corresponding branch. Debian 12 PostgreSQL 15 installations can apply package version 15.20-0+deb12u1 or later.
- How severe is CVE-2026-120139?
- CVE-2026-120139 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.59% (49th percentile) as of Nov 17, 2026.
Recent activity
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.