Skip to main content
CVE-2026-116333VulnerabilityPublished

PostgreSQL parallel B-tree scans · Buffer Over-read

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116333· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 18.7 or 17.12 when convenient.

Data as of 12 Nov 2026, 16:32 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PostgreSQL)CVSS 3.16.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 and postgresql/postgresql to 18.7 or 17.12.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.7
Fixed in
  • 18.7
PostgreSQLAffected
  • >=17 <17.12
Fixed in
  • 17.12
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • >=17 <17.12
  • >=18 <18.7
Fixed in
  • 17.12
  • 18.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vulnerability affects specific PostgreSQL versions prior to 17.12 and 18.7, upgrading to PostgreSQL 17.12 or 18.7 or later is recommended once official patches are released. Until then, monitor vendor advisories for official fixes and avoid using affected versions in sensitive environments.

Description

A buffer over-read vulnerability exists in PostgreSQL parallel B-tree scans that allows an object creator to read server memory chosen by an attacker. This occurs due to a function incorrectly marked as PARALLEL SAFE or STABLE, causing different scan-key arrays to be built by participating workers. The issue affects PostgreSQL major versions 17 and 18, specifically versions before 17.12 and 18.7. Versions prior to 17 are not affected.

References

Community reviews

Loading reviews…