CVE-2025-14179

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

May 10, 2026

Last Modified

July 25, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
Patch available. Sources: github, redhat.
redhat

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-14179.json
redhat

2468567 – (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=2468567
redhat Patch Available

CVE-2025-14179 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2025-14179
github Patch Available

SQL 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-wpvm

Vendor 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(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm19) @ xenial2026-08-23ubuntu
ubuntuphp8.1-zip (8.1.2-1ubuntu2.24) @ jammy2026-08-23ubuntu

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (26 versions)8.2.31-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1, 8.4.16-1, 8.4.16-1~deb13u1, 8.4.20-18.4.21-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1, 8.4.16-1, 8.4.16-1~deb13u1, 8.4.20-1, 8.4.21-1~deb13u18.4.21-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

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 7× in last 7d / 82× 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 313 total refreshes for this CVE.

  1. 2026-09-04 13:59 UTCEPSS rescore
  2. 2026-09-04 05:05 UTCEPSS rescore
  3. 2026-09-02 14:10 UTCEPSS rescore
  4. 2026-09-01 13:52 UTCEPSS rescore
  5. 2026-09-01 04:38 UTCEPSS rescore
  6. 2026-08-30 19:16 UTCEPSS rescore
  7. 2026-08-30 01:21 UTCEPSS rescore
  8. 2026-08-28 21:40 UTCEPSS rescore
  9. 2026-08-27 14:24 UTCEPSS rescore
  10. 2026-08-26 14:45 UTCEPSS rescore
  11. 2026-08-25 13:47 UTCEPSS rescore
  12. 2026-08-24 14:15 UTCEPSS rescore
  13. 2026-08-23 18:49 UTCEG score recompute
  14. 2026-08-23 18:49 UTCVendor advisory
  15. 2026-08-23 00:18 UTCEPSS rescore
  16. 2026-08-21 23:48 UTCEPSS rescore
  17. 2026-08-20 22:54 UTCEPSS rescore
  18. 2026-08-19 17:02 UTCEPSS rescore
  19. 2026-08-18 13:47 UTCEPSS rescore
  20. 2026-08-17 13:46 UTCEPSS rescore
  21. 2026-08-17 11:24 UTCEG score recompute
  22. 2026-08-17 11:24 UTCVendor advisory
  23. 2026-08-16 14:55 UTCEPSS rescore
  24. 2026-08-16 08:48 UTCVendor advisory
  25. 2026-08-16 04:30 UTCEG score recompute
Show 75 more
  1. 2026-08-16 04:30 UTCVendor advisory
  2. 2026-08-16 02:13 UTCEPSS rescore
  3. 2026-08-16 02:13 UTCEPSS rescore
  4. 2026-08-15 01:29 UTCEPSS rescore
  5. 2026-08-14 23:52 UTCVendor advisory
  6. 2026-08-14 19:43 UTCVendor advisory
  7. 2026-08-14 15:33 UTCVendor advisory
  8. 2026-08-14 11:24 UTCVendor advisory
  9. 2026-08-14 07:14 UTCVendor advisory
  10. 2026-08-14 03:04 UTCEG score recompute
  11. 2026-08-14 03:04 UTCVendor advisory
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-13 10:08 UTCVendor advisory
  14. 2026-08-13 05:58 UTCVendor advisory
  15. 2026-08-13 00:59 UTCVendor advisory
  16. 2026-08-12 20:49 UTCVendor advisory
  17. 2026-08-12 16:40 UTCEG score recompute
  18. 2026-08-12 16:40 UTCVendor advisory
  19. 2026-08-12 13:49 UTCEPSS rescore
  20. 2026-08-12 00:29 UTCVendor advisory
  21. 2026-08-11 20:08 UTCVendor advisory
  22. 2026-08-11 15:49 UTCEG score recompute
  23. 2026-08-11 15:49 UTCVendor advisory
  24. 2026-08-11 13:41 UTCEPSS rescore
  25. 2026-08-11 10:11 UTCVendor advisory
  26. 2026-08-11 05:23 UTCVendor advisory
  27. 2026-08-11 01:14 UTCEG score recompute
  28. 2026-08-11 01:14 UTCVendor advisory
  29. 2026-08-10 23:59 UTCEPSS rescore
  30. 2026-08-10 11:49 UTCVendor advisory
  31. 2026-08-10 07:38 UTCVendor advisory
  32. 2026-08-10 03:29 UTCVendor advisory
  33. 2026-08-09 23:19 UTCVendor advisory
  34. 2026-08-09 19:10 UTCVendor advisory
  35. 2026-08-09 15:00 UTCEG score recompute
  36. 2026-08-09 15:00 UTCVendor advisory
  37. 2026-08-09 13:45 UTCEPSS rescore
  38. 2026-08-09 10:51 UTCVendor advisory
  39. 2026-08-09 06:29 UTCVendor advisory
  40. 2026-08-09 02:20 UTCEG score recompute
  41. 2026-08-09 02:20 UTCVendor advisory
  42. 2026-08-08 13:26 UTCVendor advisory
  43. 2026-08-08 09:12 UTCVendor advisory
  44. 2026-08-08 05:02 UTCVendor advisory
  45. 2026-08-08 00:53 UTCVendor advisory
  46. 2026-08-07 20:43 UTCVendor advisory
  47. 2026-08-07 16:34 UTCEG score recompute
  48. 2026-08-07 16:34 UTCVendor advisory
  49. 2026-08-07 16:26 UTCEPSS rescore
  50. 2026-08-07 12:24 UTCVendor advisory
  51. 2026-08-07 08:14 UTCVendor advisory
  52. 2026-08-07 01:40 UTCVendor advisory
  53. 2026-08-06 19:10 UTCVendor advisory
  54. 2026-08-06 15:01 UTCEG score recompute
  55. 2026-08-06 15:01 UTCVendor advisory
  56. 2026-08-06 13:45 UTCEPSS rescore
  57. 2026-08-06 10:35 UTCVendor advisory
  58. 2026-08-06 06:23 UTCVendor advisory
  59. 2026-08-06 02:13 UTCVendor advisory
  60. 2026-08-05 22:03 UTCEG score recompute
  61. 2026-08-05 22:03 UTCVendor advisory
  62. 2026-08-05 19:16 UTCEPSS rescore
  63. 2026-08-04 15:09 UTCEPSS rescore
  64. 2026-08-04 10:37 UTCEPSS rescore
  65. 2026-08-04 03:51 UTCVendor advisory
  66. 2026-08-03 23:37 UTCVendor advisory
  67. 2026-08-03 19:28 UTCEG score recompute
  68. 2026-08-03 19:28 UTCVendor advisory
  69. 2026-08-03 10:35 UTCEPSS rescore
  70. 2026-08-03 02:14 UTCVendor advisory
  71. 2026-08-02 22:04 UTCVendor advisory
  72. 2026-08-02 17:54 UTCVendor advisory
  73. 2026-08-02 13:44 UTCVendor advisory
  74. 2026-08-02 09:33 UTCVendor advisory
  75. 2026-08-02 02:36 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-14179?
CVE-2025-14179 is a critical vulnerability published on May 10, 2026. 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…
When was CVE-2025-14179 disclosed?
CVE-2025-14179 was first published in the National Vulnerability Database on May 10, 2026, with the most recent update on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-14179 actively exploited?
CVE-2025-14179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.3% of all scored CVEs.
What is the CVSS score of CVE-2025-14179?
CVE-2025-14179 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-14179?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14179, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-14179

Explore →

Is Your Infrastructure Affected by CVE-2025-14179?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs