Skip to main content
Mallory
HighVulnerability

CVE-2026-2006: PostgreSQL Multibyte Text Buffer Overrun Leading to Code Execution

Published Feb 12, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 2 in a dayToday
CVSS8.8High · v3.1
EPSS1.1%67th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Postgresql
IdentifiersCVE-2026-2006CWE-787

CVE-2026-2006 is a buffer overrun vulnerability caused by missing validation of multibyte character lengths during PostgreSQL text manipulation. A database user can issue crafted queries that corrupt memory and execute arbitrary code with the privileges of the operating system account running PostgreSQL. Affected releases precede 18.2, 17.8, 16.12, 15.16, and 14.21 in their respective major-version branches.

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 compromises the PostgreSQL service account, potentially allowing disclosure or modification of database data and other resources accessible to that account, as well as disruption of database availability. Code execution occurs with the database service account's operating system privileges, not necessarily root or administrator privileges.

Mitigation

If you can’t patch tonight, do this now.

Until updates are applied, limit database access to trusted users and restrict network connectivity to trusted clients. Reduce opportunities for untrusted users to submit arbitrary text-manipulation queries. Apply least privilege to the PostgreSQL operating system account to limit the consequences of exploitation. These measures reduce exposure or impact but do not correct the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, or 14.21 or later within the deployed major-version branch, or install the distribution's security update containing the fix. Debian bookworm provides the fix in postgresql-15 version 15.16-0+deb12u1, and Debian trixie provides it in postgresql-17 version 17.8-0+deb13u1. For products bundling PostgreSQL, apply the relevant vendor security update.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PostgresqlPostgresqlapplication
FAQ

Frequently asked questions

Is CVE-2026-2006 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-2006 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-2006?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-2006.
Is there a patch for CVE-2026-2006?
Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, or 14.21 or later within the deployed major-version branch, or install the distribution's security update containing the fix. Debian bookworm provides the fix in postgresql-15 version 15.16-0+deb12u1, and Debian trixie provides it in postgresql-17 version 17.8-0+deb13u1.
What products are affected by CVE-2026-2006?
Postgresql.
How severe is CVE-2026-2006?
CVE-2026-2006 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 1.1% (67th percentile) as of Nov 7, 2026.
Activity feed

Recent activity

53 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+20 more in the timeline. Sign up to see them
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 activity14Community discussion across Reddit, Mastodon, and other social sources.