Skip to main content
VulnerabilityPublished

CVE-2026-100370: rhukster dom-sanitizer · Improper Input Validation

Affects rhukster dom-sanitizerSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
rhuksterdom-sanitizerAffected
  • <1.0.15
Fixed in
  • 1.0.15
GitHubrhukster/dom-sanitizerpkg:github/rhukster/dom-sanitizerOther threatsAffected
  • <1.0.15
Fixed in
  • 1.0.15

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

Community reviews

Loading reviews…