CVE-2026-116333: PostgreSQL · Buffer Over-read
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 18.7 or 17.12 when convenient.
Data as of 12 Nov 2026, 14:47 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 18.7, 17.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade PostgreSQL to 18.7 or 17.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
Upgrade affected PostgreSQL installations to version 17.12 or later if running major version 17, or to version 18.7 or later if running major version 18. These versions contain the official fixes for this vulnerability. No other mitigations are indicated.
Description
CVE-2026-116333 is a buffer over-read vulnerability in PostgreSQL affecting parallel B-tree scans. It allows an object creator to read server memory addresses chosen by an attacker due to a function incorrectly marked as PARALLEL SAFE or STABLE, causing inconsistent scan-key arrays among worker processes. This affects PostgreSQL major versions 17 and 18, specifically versions before 17.12 and 18.7. Versions prior to 17 are not affected. The vulnerability has a CVSS score of 6.5, indicating medium severity.