In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the PDO Firebird driver improperly handles NUL bytes when preparing SQL queries. During token-by-token query construction, a string token containing a NUL byte is copied via strncat(), which stops at the NUL byte, dropping the closing quote and causing subsequent SQL tokens to be interpreted as part of the string. This allows SQL injection when attacker-controlled values are quoted via PDO::quote() and embedded in SQL statements.
CVE-2025-14179
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EPSS
- 21.7%
- KEV
- Not listed
Published
May 10, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 12, 2026Affected: Red Hat Enterprise Linux 10",
https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-14179.json2468567 – (CVE-2025-14179) CVE-2025-14179 php: SQL injection in pdo_firebird via NUL bytes in quoted strings
https://bugzilla.redhat.com/show_bug.cgi?id=2468567SQL injection in pdo_firebird via NUL bytes in quoted strings · Advisory · php/php-src · GitHub
https://github.com/php/php-src/security/advisories/GHSA-w476-322c-wpvmVendor Advisories for CVE-2025-14179(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | php8.4-zip (8.4.11-1ubuntu1.2) @ questing | 2026-06-28 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 14× in last 7d / 64× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 284 total refreshes for this CVE.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:25 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-15 02:06 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-08 15:14 UTCEPSS rescore
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 08:54 UTCEG score recompute
- 2026-06-28 08:54 UTCVendor advisory
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-28 03:38 UTCEG score recompute
- 2026-06-28 03:38 UTCVendor advisory
- 2026-06-27 14:41 UTCEG score recompute
- 2026-06-27 14:41 UTCVendor advisory
- 2026-06-27 10:25 UTCEG score recompute
- 2026-06-27 10:25 UTCVendor advisory
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 21:10 UTCEG score recompute
- 2026-06-26 21:10 UTCVendor advisory
- 2026-06-26 05:42 UTCEG score recompute
- 2026-06-26 05:42 UTCVendor advisory
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-23 21:32 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:52 UTCEPSS rescore
- 2026-06-17 05:39 UTCEG score recompute
- 2026-06-17 05:39 UTCVendor advisory
- 2026-06-17 01:11 UTCEG score recompute
- 2026-06-17 01:11 UTCVendor advisory
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 07:49 UTCEG score recompute
- 2026-06-16 07:49 UTCVendor advisory
- 2026-06-15 17:48 UTCEPSS rescore
- 2026-06-15 08:03 UTCEG score recompute
- 2026-06-15 08:03 UTCVendor advisory
- 2026-06-15 03:34 UTCEG score recompute
- 2026-06-15 03:34 UTCVendor advisory
- 2026-06-14 23:25 UTCEG score recompute
- 2026-06-14 23:25 UTCVendor advisory
- 2026-06-14 23:17 UTCEPSS rescore
- 2026-06-14 19:15 UTCEG score recompute
- 2026-06-14 19:15 UTCVendor advisory
- 2026-06-14 15:06 UTCEG score recompute
- 2026-06-14 15:06 UTCVendor advisory
- 2026-06-14 10:53 UTCEG score recompute
- 2026-06-14 10:53 UTCVendor advisory
- 2026-06-14 06:43 UTCEG score recompute
- 2026-06-14 06:43 UTCVendor advisory
- 2026-06-14 02:15 UTCEG score recompute
- 2026-06-14 02:15 UTCVendor advisory
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-13 09:00 UTCEG score recompute
- 2026-06-13 09:00 UTCVendor advisory
- 2026-06-13 02:54 UTCEG score recompute
- 2026-06-13 02:54 UTCVendor advisory
- 2026-06-12 23:11 UTCEPSS rescore
- 2026-06-12 22:43 UTCEG score recompute
- 2026-06-12 22:43 UTCVendor advisory
- 2026-06-12 18:31 UTCEG score recompute
- 2026-06-12 18:31 UTCVendor advisory
- 2026-06-12 14:15 UTCEG score recompute
- 2026-06-12 14:15 UTCVendor advisory
- 2026-06-12 09:47 UTCEG score recompute
- 2026-06-12 09:47 UTCVendor advisory
- 2026-06-12 05:35 UTCEG score recompute
- 2026-06-12 05:35 UTCVendor advisory
- 2026-06-12 01:26 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
Frequently asked(5)
What is CVE-2025-14179?
When was CVE-2025-14179 disclosed?
Is CVE-2025-14179 actively exploited?
What is the CVSS score of CVE-2025-14179?
How do I remediate CVE-2025-14179?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-14179
Is Your Infrastructure Affected by CVE-2025-14179?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.