CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (8.8). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain 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.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | postgresql-15 | no fix listed | DEBIAN-CVE-2026-120139 |
| Debian | 13 | postgresql-17 | 17.12-0+deb13u1 | DEBIAN-CVE-2026-120139 |
| Debian | 14 | postgresql-18 | no fix listed | DEBIAN-CVE-2026-120139 |
| Ubuntu | 20.04:LTS | postgresql-12 | no fix listed | UBUNTU-CVE-2026-120139 |
| Ubuntu | 22.04:LTS | postgresql-14 | no fix listed | UBUNTU-CVE-2026-120139 |
| Ubuntu | 24.04:LTS | postgresql-16 | no fix listed | UBUNTU-CVE-2026-120139 |
| Ubuntu | 26.04:LTS, 26.10 | postgresql-18 | no fix listed | UBUNTU-CVE-2026-120139 |
| Ubuntu | Pro:14.04:LTS | postgresql-9.3 | no fix listed | UBUNTU-CVE-2026-120139 |
| Ubuntu | Pro:16.04:LTS | postgresql-9.5 | no fix listed | UBUNTU-CVE-2026-120139 |
| Ubuntu | Pro:18.04:LTS | postgresql-10 | no fix listed | UBUNTU-CVE-2026-120139 |
| Red Hat | hummingbird:1 | libpq, libpq-devel | 0:18.7-0.1.hum1 | RHSA-2026:99821 |
| Alpine | v3.21, v3.22 | postgresql15 | 15.20-r0 | ALPINE-CVE-2026-120139 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql16 | 16.16-r0 | ALPINE-CVE-2026-120139 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql17 | 17.12-r0 | ALPINE-CVE-2026-120139 |
| Alpine | v3.23, v3.24 | postgresql18 | 18.7-r0 | ALPINE-CVE-2026-120139 |
| Azure Linux | 3 | postgresql | no fix listed | AZL-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | libpq | Affected | |
| Red Hat Hardened Images | postgresql17 | Affected | |
| Red Hat Hardened Images | postgresql18 | Affected |
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.