CVSS 3.1
4.3 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NCVE-2026-116310 PostgreSQL COPY error context uses freed field storage
Medium (4.3). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Use after free in PostgreSQL COPY FROM error reporting allows a database user to disclose portions of server memory, via a longer input row following an ignored or nullified conversion error. file_fdw reaches the same code path in affected version 18. Within major versions 17-18, minor versions before PostgreSQL 18.7 and 17.12 are affected. Versions before PostgreSQL 17 are unaffected.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-416 Use After Free
- Published
- Modified
- Assigned by
- PostgreSQL (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-116310 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116310?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116310?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-116310 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
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:
[](https://cve.bz/cve/CVE-2026-116310)
HTML:
<a href="https://cve.bz/cve/CVE-2026-116310"><img src="https://cve.bz/cve/badge/CVE-2026-116310.svg" alt="CVE-2026-116310"></a>
Fix and patched versions
- Debian, Red Hat, Alpine: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | postgresql-15 | no fix listed | DEBIAN-CVE-2026-116310 |
| Debian | 13 | postgresql-17 | 17.12-0+deb13u1 | DEBIAN-CVE-2026-116310 |
| Debian | 14 | postgresql-18 | no fix listed | DEBIAN-CVE-2026-116310 |
| Ubuntu | 20.04:LTS | postgresql-12 | no fix listed | UBUNTU-CVE-2026-116310 |
| Ubuntu | 22.04:LTS | postgresql-14 | no fix listed | UBUNTU-CVE-2026-116310 |
| Ubuntu | 24.04:LTS | postgresql-16 | no fix listed | UBUNTU-CVE-2026-116310 |
| Ubuntu | 26.04:LTS, 26.10 | postgresql-18 | no fix listed | UBUNTU-CVE-2026-116310 |
| Ubuntu | Pro:14.04:LTS | postgresql-9.3 | no fix listed | UBUNTU-CVE-2026-116310 |
| Ubuntu | Pro:16.04:LTS | postgresql-9.5 | no fix listed | UBUNTU-CVE-2026-116310 |
| Ubuntu | Pro:18.04:LTS | postgresql-10 | no fix listed | UBUNTU-CVE-2026-116310 |
| 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-116310 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql16 | 16.16-r0 | ALPINE-CVE-2026-116310 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql17 | 17.12-r0 | ALPINE-CVE-2026-116310 |
| Alpine | v3.23, v3.24 | postgresql18 | 18.7-r0 | ALPINE-CVE-2026-116310 |
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. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.
Red Hat
Red Hat rates this Moderate.
This vulnerability is rated as having Moderate impact because exploitation is constrained to reading uninitialized or previously freed server memory and requires an authenticated database user with permissions to execute data import commands. While an attacker cannot modify database records or disrupt service availability directly, the leaked memory contents may disclose sensitive environment or query data. Standard enterprise deployments running versions prior to PostgreSQL 17 do not contain the affected error-handling logic and remain unaffected.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| 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-116310.