CVE-2026-116333: Server-memory disclosure in PostgreSQL parallel B-tree array scans
CVE-2026-116333 is a buffer over-read in PostgreSQL parallel B-tree scans involving array keys. A function incorrectly marked PARALLEL SAFE or STABLE can cause participating workers to construct different scan-key arrays, resulting in reads beyond array bounds. An attacker with object-creation privileges can exploit this inconsistency to read attacker-chosen server-memory addresses. PostgreSQL 17 before 17.12 and PostgreSQL 18 before 18.7 are affected; versions before PostgreSQL 17 are unaffected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation discloses server memory at attacker-chosen addresses, potentially exposing sensitive information otherwise inaccessible to the database user. The vulnerability has a CVSS v3.1 score of 6.5, reflecting high confidentiality impact with no identified integrity or availability impact.
Mitigation
If you can’t patch tonight, do this now.
Until patched, prevent affected queries from executing parallel B-tree array scans and restrict untrusted users' ability to create or alter functions with PARALLEL SAFE or STABLE markings. Any parallel-execution restriction must be enforced so that potentially malicious database users cannot override it.
Remediation
Patch, then assume compromise.
Upgrade PostgreSQL 17 installations to version 17.12 or later, or PostgreSQL 18 installations to version 18.7 or later. Apply the corresponding vendor security-update packages when using distribution-maintained builds.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-116333 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-116333 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-116333?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-116333.
- Is there a patch for CVE-2026-116333?
- Upgrade PostgreSQL 17 installations to version 17.12 or later, or PostgreSQL 18 installations to version 18.7 or later. Apply the corresponding vendor security-update packages when using distribution-maintained builds.
- How severe is CVE-2026-116333?
- CVE-2026-116333 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.37% (32nd percentile) as of Nov 16, 2026.
Recent activity
10 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.