Loading vulnerability…
CVE-2025-12818 is an integer wraparound vulnerability in PostgreSQL's libpq client library affecting multiple escaping routines centered on PQescapeInternal, which is used by PQescapeLiteral and PQescapeIdentifier. When libpq processes an extremely large input string containing large numbers of quote or backslash characters, signed integer counters used during escaping can overflow. The overflow causes libpq to miscalculate the required output buffer size, allocate a buffer that is too small, and then write escaped output past the end of that allocation by a very large margin. The flaw is present in PostgreSQL versions before 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23.
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.
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.