CVE-2026-7258

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% 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
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: 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, some functions, including urldecode(), pass signed char to ctype functions (like isxdigit()). On the systems with default signed char and optimized table-lookup ctype functions - such as NetBSD - this can lead to accessing array with negative offset, which can trigger a denial of service.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

May 10, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated May 10, 2026
Patch available. Sources: github.
github Patch Available

Out-of-bounds read in urldecode() · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-m8rr-4c36-8gq4

Vendor Advisories for CVE-2026-7258(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatphp:7.4-8100020260604072603.f79986652026-07-01redhat
redhatphp-0:8.0.30-6.el9_82026-06-30redhat
redhatphp-0:8.3.31-1.el10_22026-06-04redhat
redhatphp8.4-0:8.4.21-1.el10_22026-06-02redhat
redhatphp:8.2-9080020260521080715.92026-06-01redhat
redhatphp:8.3-9080020260521113736.92026-06-01redhat
redhatphp:8.2-8100020260521052503.f79986652026-06-01redhat
redhatphp-main-8.5.6-1.hum12026-05-06redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
php7.47.4.21-1+deb11u1 ... 7.4.33-1+deb11u9 (14 versions)7.4.33-1+deb11u11—
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.

Data Freshness Timeline

(refreshed 8× 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 189 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-7258?
CVE-2026-7258 is a high 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, some functions, including urldecode(), pass signed char to ctype functions (like isxdigit()). On the systems with default signed char and optimized table-lookup ctype functions - such as NetBSD - this…
When was CVE-2026-7258 disclosed?
CVE-2026-7258 was first published in the National Vulnerability Database on May 10, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7258 actively exploited?
CVE-2026-7258 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 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-7258?
CVE-2026-7258 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-7258?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7258, 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-2026-7258

Explore →

Is Your Infrastructure Affected by CVE-2026-7258?

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

Start Free Scan →Browse All CVEs