CVE-2026-100370

MEDIUMPre-NVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th 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
Elevated

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

4.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

DOMSanitizer is a DOM/SVG/MathML Sanitizer for PHP 7.3+. Prior to version 1.0.15, the isDangerousUrl() method is responsible for rejecting dangerous URL values in the href and xlink:href attributes. The weakness is that "javascript:" is rejected as a scheme, while "data:" is rejected only when the literal substring onload appears in the URL value (/^data:.*onload/i). Because data: payloads are routinely Base64-encoded, the dangerous content (, event handlers, etc.) is invisible to that substring test. A URL such as data:text/html;base64,… therefore survives in href / xlink:href, even though the decoded payload is active markup. This is an incomplete input-validation / sanitization defect in the sanitizer itself. This issue has been patched in version 1.0.15.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
37
EG Risk 37/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
19th
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 28, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 28, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub release Patch Available

1.0.15

Patch available: rhukster/dom-sanitizer 1.0.15

https://github.com/rhukster/dom-sanitizer/releases/tag/1.0.15
GitHub commit Patch Available

commit fb8f758b4113 (rhukster/dom-sanitizer)

Patch available: rhukster/dom-sanitizer 1.0.15 (contains commit fb8f758b4113)

https://github.com/rhukster/dom-sanitizer/commit/fb8f758b41134fc5fb2f563666f2330c69e31f94
GitHub commit Patch Available

commit 10f97807e450 (rhukster/dom-sanitizer)

Patch available: rhukster/dom-sanitizer 1.0.15 (contains commit 10f97807e450)

https://github.com/rhukster/dom-sanitizer/commit/10f97807e4501d60f63987f2e76a38cdbf312dcb
GitHub advisoryMentions a patch (unverified)

Incomplete data: URL Sanitization in DOMSanitizer::isDangerousUrl() Allows Base64-Encoded Payloads to Bypass href and xlink:href Validation · Advisory · rhukster/dom-sanitizer · GitHub

https://github.com/rhukster/dom-sanitizer/security/advisories/GHSA-wcj2-r6vg-rm97

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-31 12:55 UTCOSV refresh
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-25 15:58 UTCEG score recompute
  11. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-23 09:54 UTCEG score recompute
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-18 05:11 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-12 16:42 UTCEG score recompute
Show 29 more
  1. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-11 19:34 UTCEG score recompute
  3. 2026-10-11 18:29 UTCEG score recompute
  4. 2026-10-11 15:03 UTCEG score recompute
  5. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-10 19:41 UTCEG score recompute
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-08 19:53 UTCEG score recompute
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-06 19:22 UTCEG score recompute
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-05 19:29 UTCEG score recompute
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-03 19:42 UTCEG score recompute
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-02 19:49 UTCEG score recompute
  20. 2026-10-01 19:55 UTCEG score recompute
  21. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-30 20:02 UTCEG score recompute
  23. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-09-29 23:45 UTCEG score recompute
  25. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-28 21:18 UTCEG score recompute
  27. 2026-09-28 20:46 UTCEG score recompute
  28. 2026-09-28 20:26 UTCEG score recomputeFirst assessed: 4.7 MEDIUM
  29. 2026-09-28 20:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100370?
CVE-2026-100370 is a medium-severity vulnerability; its CVE record was published on September 28, 2026. DOMSanitizer is a DOM/SVG/MathML Sanitizer for PHP 7.3+. Prior to version 1.0.15, the isDangerousUrl() method is responsible for rejecting dangerous URL values in the href and xlink:href attributes. The weakness is that "javascript:" is rejected as a scheme, while "data:" is rejected only when the…
When was the CVE record for CVE-2026-100370 published?
The CVE record for CVE-2026-100370 was published on September 28, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-100370 actively exploited?
CVE-2026-100370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100370?
CVE-2026-100370 has a CVSS base score of 4.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100370?
A fix for CVE-2026-100370 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100370

Explore →

Is Your Infrastructure Affected by CVE-2026-100370?

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

Book a Demo →Browse All CVEs