CVE-2026-25290 is a denial-of-service vulnerability in PHP’s pdo_pgsql driver. The flaw is reachable when an application explicitly enables emulated prepared statements and passes a query parameter containing a byte sequence that is invalid for the active PostgreSQL connection character encoding. In this condition, PostgreSQL’s client library may fail silently and return a NULL escaped string rather than a valid escaped value. PDO’s query handling logic then attempts to read the length of that NULL value, resulting in a null-pointer dereference and an immediate crash of the PHP process. The issue affects the interaction between PDO’s emulated prepare path and libpq error handling for malformed multibyte input.
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.
2 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.