CVE-2026-7261

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (22nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-28970 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 10, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Oct 31, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphp8.4-zip (8.4.11-1ubuntu1.2) @ questing2026-11-01ubuntu
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm19) @ xenial2026-11-01ubuntu
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 rangeFix by version rangeDependents
php7.47.4.21-1+deb11u1 ... 7.4.33-1+deb11u9 (14 versions)
  • every version up to 7.4.33-1+deb11u11: fixed in 7.4.33-1+deb11u11
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (26 versions)
  • every version up to 8.2.31-1~deb12u1: fixed in 8.2.31-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1, 8.4.16-1, 8.4.16-1~deb13u1, 8.4.20-1
  • every version up to 8.4.21-1~deb13u1: fixed in 8.4.21-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1, 8.4.16-1, 8.4.16-1~deb13u1, 8.4.20-1, 8.4.21-1~deb13u1
  • every version up to 8.4.21-1: fixed in 8.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 21× in last 7d / 76× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 386 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 288 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-7261?
CVE-2026-7261 is a critical-severity vulnerability; its CVE record was 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 SOAP_PERSISTENCE_SESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the…
When was CVE-2026-7261 made public?
CVE-2026-7261 was made public on May 7, 2026: that is the date its CVE record's CNA, PHP Group, gives for when the vulnerability was made public. The CVE record itself was published on May 10, 2026. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-7261 actively exploited?
CVE-2026-7261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-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?
A fix for CVE-2026-7261 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7261 are linked in the Vendor Advisories panel on this page.

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.