Read the docs

Buffer over-read in PostgreSQL parallel B-tree scans

Priority LOW 29CWE-126Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Partial Red Hat: 1 fixed, 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-126 and the CVSS impact.

Summary

PostgreSQL 18 before 18.7 and 17 before 17.12 are affected, while versions before 17 are unaffected. A buffer over-read in parallel B-tree scans (CWE-126) lets an object creator read server memory at attacker-chosen addresses. The attacker uses a function incorrectly marked PARALLEL SAFE or STABLE, which makes participating workers build different scan-key arrays.

Written with Claude Haiku 5.5 from the sources below · 2026-11-14

Description from the CNA

Buffer over-read in PostgreSQL parallel B-tree scans allows an object creator to read attacker-chosen server-memory addresses, via a function incorrectly marked PARALLEL SAFE or STABLE to make participating workers build different scan-key arrays. Within major versions 17-18, minor versions before PostgreSQL 18.7 and 17.12 are affected. Versions before PostgreSQL 17 are unaffected.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00371 31st percentileScored 2026-11-16
Fix Partial PostgreSQL: 18.7, 17.12Red Hat: 1 advisoryRed Hat: 1 fixed, 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
—PostgreSQL18 to before 18.7; 17 to before 17.1218.7, 17.12Patch availableCNA
  • PostgreSQL Vendor— Affected 18 to before 18.7; 17 to before 17.12 Fixed in 18.7, 17.12 Patch available CNA

Remediation

Upgrade PostgreSQL 18 to 18.7 or PostgreSQL 17 to 17.12. Red Hat fixes Red Hat Hardened Images with RHSA-2026:99821, but lists Red Hat Hardened Images as affected without a fix, with plan none_available.

Written with Claude Haiku 5.5 from the sources below · 2026-11-14

  • Fix · CNA PostgreSQL Fixed in 18.7, 17.12

Red Hat 1 advisory

  • RHSA-2026:99821 Released 2026-11-12 · Red Hat rating Important
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images libpq-18.7-0.1.hum1@aarch64, libpq-18.7-0.1.hum1@s390x, libpq-18.7-0.1.hum1@src +4

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    PostgreSQL 17.12, 18.7

    4 records Highest priority Priority MEDIUM 1 MEDIUM, 3 LOW

    Other records, highest priority first

    • TI-2026-90375 Type confusion in PostgreSQL record types lets users run codePriority MEDIUM 41
    • TI-2026-90362 SQL injection in PostgreSQL reindexdb lets object creators run SQLPriority LOW 35
    • TI-2026-90348 Use after free in PostgreSQL COPY errors discloses server memoryPriority LOW 20

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Hardened ImagesAffectedNo fix yet
Red Hat Hardened ImagesFixed RHSA-2026:99821

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-116333
  2. 2026-11-12 Alias added: GHSA-gjgq-ff5c-x6hp
  3. 2026-11-12 Affected versions changed · Red Hat
  4. 2026-11-12 CVSS score added · Red Hat
  5. 2026-11-12 CISA SSVC decision points changed
  6. 2026-11-13 Fix available: RHSA-2026:99821 · Red Hat
  7. 2026-11-14 Fix available: Red Hat Hardened Images · Red Hat

References

Sources