CVE-2025-12818 is an integer-wraparound flaw in PostgreSQL's libpq client library. PQescapeInternal, which underlies PQescapeLiteral and PQescapeIdentifier, uses signed integer counters while counting quote and backslash characters in caller-controlled input. An extremely large input containing sufficient quote or backslash characters can overflow these counters, causing an undersized output-buffer allocation followed by out-of-bounds writes during construction of the escaped string. PostgreSQL versions earlier than 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 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.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Specific vulnerability referenced as affecting VMware Photon OS 5.0 PostgreSQL 15 package; exploit availability is indicated, but no technical details are provided in the content.
Integer overflow in PostgreSQL libpq’s PQescapeInternal leading to incorrect buffer size calculation, heap buffer overflow/out-of-bounds write and resulting crash (segmentation fault), demonstrated as reachable via PHP’s pdo_pgsql escapeIdentifier path.
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.