Skip to main content
Mallory
MediumVulnerability

CVE-2026-116333: Server-memory disclosure in PostgreSQL parallel B-tree array scans

Published Nov 12, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS0.37%32nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-116333CWE-125

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

10 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.