CVE-2026-100370: rhukster dom-sanitizer · Improper Input Validation
Affects rhukster dom-sanitizerSource CVE Database V5
Not known to be exploited · CVSS 4.7 Medium : upgrade to 1.0.15 when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.15
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade dom-sanitizer and rhukster/dom-sanitizer to 1.0.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rhuksterdom-sanitizer | Affected
| Fixed in
|
GitHubrhukster/dom-sanitizerpkg:github/rhukster/dom-sanitizerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in DOMSanitizer version 1.0.15. Users should upgrade to version 1.0.15 or later to ensure proper URL validation and sanitization. No additional mitigation is required if the upgrade is applied.
Description
DOMSanitizer versions prior to 1.0.15 have an input validation flaw in the isDangerousUrl() method. The sanitizer rejects 'javascript:' URLs but only partially rejects 'data:' URLs by checking for the literal substring 'onload'. Because data: payloads are often Base64-encoded, dangerous content can bypass this check and remain in href or xlink:href attributes. This incomplete sanitization could allow active markup to persist. The issue is fixed in version 1.0.15.
References
- github.com/rhukster/dom-sanitizer/security/advisories/GHSA-wcj2-r6vg-rm97 (opens in a new tab)
- github.com/rhukster/dom-sanitizer/commit/10f97807e4501d60f63987f2e76a38cdbf312dcb (opens in a new tab)
- github.com/rhukster/dom-sanitizer/commit/fb8f758b41134fc5fb2f563666f2330c69e31f94 (opens in a new tab)
- github.com/rhukster/dom-sanitizer/releases/tag/1.0.15 (opens in a new tab)