CVE-2026-116321: PostgreSQL unterminated name value discloses server memory
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a PostgreSQL 14.25, 15.20, 16.16; azl3 postgresql 16.15-1 on Azure Linux 3.0 Release Notes; azl4 libecpg 16.4-6.azl4 on Azure Linux 4.0 Release Notes.
Low priority for now. Upgrade to n/a PostgreSQL 14.25, 15.20, 16.16; azl3 postgresql 16.15-1 on Azure Linux 3.0 Release Notes; azl4 libecpg 16.4-6.azl4 on Azure Linux 4.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as a C string. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
- Published
- Nov 12, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-170
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.
n/a PostgreSQL
- 18 and later · before 18.7affected · rpm
- 17 and later · before 17.12affected · rpm
- 16 and later · before 16.16affected · rpm
- 15 and later · before 15.20affected · rpm
- before 14.25affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | postgresql15 | before 15.20-r0 | 15.20-r0 |
| Alpine:v3.21 | postgresql16 | before 16.16-r0 | 16.16-r0 |
| Alpine:v3.21 | postgresql17 | before 17.12-r0 | 17.12-r0 |
| Alpine:v3.23 | postgresql18 | before 18.7-r0 | 18.7-r0 |
| Debian:12 | postgresql-15 | before 15.20-0+deb12u1 | 15.20-0+deb12u1 |
| Debian:13 | postgresql-17 | before 17.12-0+deb13u1 | 17.12-0+deb13u1 |
| Debian:14 | postgresql-18 | from 0 | — |
| openSUSE:Tumbleweed | postgresql14 | before 14.25-1.1 | 14.25-1.1 |
| openSUSE:Tumbleweed | postgresql15 | before 15.20-1.1 | 15.20-1.1 |
| openSUSE:Tumbleweed | postgresql16 | before 16.16-1.1 | 16.16-1.1 |
| openSUSE:Tumbleweed | postgresql17 | before 17.12-1.1 | 17.12-1.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a PostgreSQL | 14.25 | Vendor (CNA) |
| n/a PostgreSQL | 15.20 | Vendor (CNA) |
| n/a PostgreSQL | 16.16 | Vendor (CNA) |
| n/a PostgreSQL | 17.12 | Vendor (CNA) |
| n/a PostgreSQL | 18.7 | Vendor (CNA) |
| azl3 postgresql 16.15-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl4 libecpg 16.4-6.azl4 on Azure Linux 4.0 | Release Notes | Microsoft (MSRC) |
| azl4 postgresql17 17.11-5.azl4 on Azure Linux 4.0 | Release Notes | Microsoft (MSRC) |
| azl4 postgresql18 18.6-5.azl4 on Azure Linux 4.0 | Release Notes | Microsoft (MSRC) |
| alpine:postgresql15 | 15.20-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql16 | 16.16-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql17 | 17.12-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql18 | 18.7-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:postgresql-15 | 15.20-0+deb12u1 · Debian:12 | Package registry (OSV) |
| debian:postgresql-17 | 17.12-0+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:postgresql14 | 14.25-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql15 | 15.20-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql16 | 16.16-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql17 | 17.12-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+4 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-170 · Improper Null TerminationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.