CVE-2026-91765

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

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

7.5EG
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

cleanup_xml_node() in the SOAP XML parser recurses once per XML nesting level with no depth limit. An unauthenticated attacker can post a SOAP request containing tens of thousands of nested elements to any SoapServer endpoint, exhaust the stack and crash the process. The same unbounded recursion exists in the SOAP value decoder and in the WSDL node search helper.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
31st
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

September 25, 2026

Last Modified

October 23, 2026

Advisory Details (1)

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

SOAP: Unbounded Recursion in Server-Side cleanup_xml_node · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-rgrp-mwpx-f6rm

Vendor Advisories for CVE-2026-91765(9)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphp7.2-zip (7.2.24-0ubuntu0.18.04.17+esm13) @ bionic2026-10-29ubuntu
redhatphp:8.3-9080020261020115403.92026-10-21redhat
redhatphp-0:8.0.30-8.el9_8.12026-10-21redhat
redhatphp-0:8.3.36-1.el10_22026-10-21redhat
redhatphp:7.4-8100020261021081045.f79986652026-10-21redhat
redhatphp8.4-0:8.4.27-1.el10_22026-10-21redhat
redhatphp:8.2-8100020261020140951.f79986652026-10-21redhat
redhatphp:8.2-9080020261020145734.92026-10-21redhat
redhatphp-main-8.5.11-2.hum12026-09-23redhat

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 rangeFix by version rangeDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (29 versions)
  • every version up to 8.2.34-1~deb12u1: fixed in 8.2.34-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1 ... 8.4.24-1~deb13u1 (11 versions)
  • every version up to 8.4.26-1~deb13u1: fixed in 8.4.26-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1 ... 8.4.26-1~deb13u1 (12 versions)
  • every version up to 8.4.26-1: fixed in 8.4.26-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 9× in last 7d / 67× 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.

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. 1 repeat row among the latest 100 is merged into the row it repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-91765?
CVE-2026-91765 is a high-severity vulnerability; its CVE record was published on September 25, 2026. cleanup_xml_node() in the SOAP XML parser recurses once per XML nesting level with no depth limit. An unauthenticated attacker can post a SOAP request containing tens of thousands of nested elements to any SoapServer endpoint, exhaust the stack and crash the process. The same unbounded recursion…
When was the CVE record for CVE-2026-91765 published?
The CVE record for CVE-2026-91765 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-91765 actively exploited?
CVE-2026-91765 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91765?
CVE-2026-91765 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91765?
A fix for CVE-2026-91765 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-91765 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-91765

Explore →

Is Your Infrastructure Affected by CVE-2026-91765?

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

Book a Demo →Browse All CVEs