cve.bz

CVE-2026-120139 PostgreSQL tuple-size integer wraparound executes arbitrary code

8.8 highEPSS 0.6%

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

On this page
Integer wraparound in PostgreSQL in-memory tuple-size calculations allows a database user to execute arbitrary code as the operating system user running the database, via oversized tuple data. 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:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 49th 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-12. 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-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
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-120139 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120139?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120139?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-120139 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-120139

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-120139](https://cve.bz/cve/badge/CVE-2026-120139.svg)](https://cve.bz/cve/CVE-2026-120139)

HTML:

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

Fix and patched versions

Linux distributions

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

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

This vulnerability is rated as an Important impact by Red Hat Product Security because an authenticated database user can achieve arbitrary code execution within the context of the postgres system user, compromising host and database integrity. While standard deployments on Red Hat Enterprise Linux confine the database process using a dedicated service account and SELinux, exploitation fully exposes the database engine and any data accessible to it. Exploitation requires network reachability and valid database login credentials to submit queries containing crafted, oversized row records. Unauthenticated remote attackers cannot trigger this issue directly.

Red Hat's mitigation

Restrict network exposure to the PostgreSQL service so that only trusted client hosts and authorized administrators can establish connections.

1. Using firewalld, restrict incoming connections on PostgreSQL port 5432 to a trusted IP address or subnet:

```

firewall-cmd --permanent --remove-service=postgresql

firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_RANGE>

firewall-cmd --reload

```

2. Alternatively, configure PostgreSQL to bind only to local interfaces by modifying `listen_addresses` in `/var/lib/pgsql/data/postgresql.conf`:

```

listen_addresses = 'localhost'

```

Apply the configuration change by restarting the service:

```

systemctl restart postgresql

```

Caveats:

Restricting network connectivity or interface binding prevents remote clients and applications outside the allowed subnet from connecting to the database.

Warning:

Restarting or reloading the PostgreSQL service terminates active client connections and temporarily interrupts database availability.

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-120139.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

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

References

Check your stackJSON