CVE-2026-14679 is a stack-based buffer overflow in PostgreSQL argument-name matching. An object creator can manipulate an OUT-parameter count to cause writes beyond a stack buffer in server memory. The out-of-bounds writes are constrained to byte values 0x00 and 0x01. PostgreSQL versions before 18.6, 17.11, 16.15, 15.19, and 14.24 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.
27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL stack-buffer-overflow vulnerability involving manipulation of the OUT parameter count.
A PostgreSQL vulnerability referenced by the plugin; no technical vulnerability details are provided.
A PostgreSQL argument-matching stack-buffer-overflow flaw that can write 0x0 and 0x1 to server memory.
A PostgreSQL argument-matching stack buffer overflow that writes zero or one values to server memory.
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.