CVE-2026-7261

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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
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, when SoapServer is configured with SOAP_PERSISTENCE_SESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the persistance is handled incorrectly, resulting in freeing the object while keeping a pointer to it, which may lead to use-after-free. This may lead to memory corruption, information disclosure, or process crashes, with confidentiality, integrity, and availability impact on the vulnerable system.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

May 10, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Aug 21, 2026
Patch available. Sources: github.
github Patch Available

SoapServer session-persisted object use-after-free via SOAP header fault · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm19) @ xenial2026-08-23ubuntu
ubuntuphp8.5-zip (8.5.4-0ubuntu1.1) @ resolute2026-08-23ubuntu
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

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.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-7261?
CVE-2026-7261 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, when SoapServer is configured with SOAPPERSISTENCESESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the persistance…
When was CVE-2026-7261 disclosed?
CVE-2026-7261 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-7261 actively exploited?
CVE-2026-7261 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 77.8% of all scored CVEs.
What is the CVSS score of CVE-2026-7261?
CVE-2026-7261 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-7261?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7261, 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-7261

Explore →

Is Your Infrastructure Affected by CVE-2026-7261?

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