Skip to main content
Mallory
HighVulnerability

CVE-2026-25290: NULL Pointer Dereference in PHP PDO PostgreSQL Driver

Published Sep 17, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.10%1st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
QualcommPHP Group
IdentifiersCVE-2026-25290CWE-476

CVE-2026-25290 is a denial-of-service vulnerability in PHP's PDO PostgreSQL driver (pdo_pgsql). When emulated prepared statements are explicitly enabled, a query parameter containing a byte sequence invalid for the active PostgreSQL connection encoding can cause libpq to return a NULL escaped-string value. PDO subsequently attempts to obtain the length of that value without first verifying that it is non-NULL, resulting in a NULL pointer dereference and PHP process segmentation fault.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker able to supply a malformed parameter value to an affected application can terminate the PHP process handling the request, causing denial of service. If the crash occurs during a non-atomic workflow, such as after an external payment debit but before the corresponding order record is committed, it may also leave application or transactional state inconsistent.

Mitigation

If you can’t patch tonight, do this now.

Disable PDO emulated prepared statements for PostgreSQL where they are not required. Validate or reject input that is not valid for the configured database connection encoding before it reaches PDO. Use atomic database transactions for state-changing workflows so that failures roll back incomplete operations.

Remediation

Patch, then assume compromise.

Update PHP to a release containing the fix for CVE-2026-25290. The fix checks whether the escaped value returned by libpq is NULL before dereferencing it and converts the condition into a catchable application error. Specific fixed version numbers are not available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PHP GroupPhpapplication
QualcommCologne Firmwareoperating_system
QualcommFastconnect 7800 Firmwareoperating_system
QualcommSnapdragon X2 Elite Firmwareoperating_system
QualcommWcd9378c Firmwareoperating_system
QualcommWsa8840 Firmwareoperating_system
QualcommWsa8845 Firmwareoperating_system
QualcommWsa8845h Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2026-25290 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-25290 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25290?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-25290.
Is there a patch for CVE-2026-25290?
Update PHP to a release containing the fix for CVE-2026-25290. The fix checks whether the escaped value returned by libpq is NULL before dereferencing it and converts the condition into a catchable application error.
What products are affected by CVE-2026-25290?
PHP Group Php, Qualcomm Cologne Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Snapdragon X2 Elite Firmware, Qualcomm Wcd9378c Firmware, and 3 more.
How severe is CVE-2026-25290?
CVE-2026-25290 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.10% (1st percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.