Loading vulnerability…
CVE-2026-2006 is an out-of-bounds write vulnerability in PostgreSQL multibyte text handling, including the pgcrypto symmetric-decryption path. Insufficient validation of multibyte character lengths permits malformed UTF-8 data to reach string-processing routines, causing a buffer overrun during crafted query processing. A database user can leverage the resulting memory corruption to execute arbitrary code as the operating-system account that runs the PostgreSQL server. PostgreSQL versions earlier than 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A prior PostgreSQL vulnerability cited only as having related code heritage to the heap buffer overflow discussed in this notice.
Previously fixed PostgreSQL vulnerability referenced as background for similar defect classes.
Prior PostgreSQL vulnerability referenced only as a fix for a similar defect class.
Prior PostgreSQL vulnerability mentioned solely for comparison with related encoding and buffer-read defects.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.