CVE-2026-44990 is a sanitizer bypass in sanitize-html's default handling of disallowed tags. In the default disallowedTagsMode: 'discard' path, attacker-controlled content placed within a disallowed xmp element can be emitted as active HTML or JavaScript rather than safely discarded or escaped. Applications that subsequently render this sanitized result as trusted HTML can expose users to stored cross-site scripting. The published affected range is sanitize-html versions prior to 2.17.4; an unconfirmed report suggests the regression may have been introduced in 2.17.3 specifically.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A prior sanitize-html vulnerability/fix related to xmp default handling; it did not remediate the literal-solidus RCDATA end-tag parser differential described in CVE-2026-63670.
A sanitizer bypass vulnerability in sanitize-html prior to version 2.17.4 that can allow attacker-controlled content in a disallowed xmp element to become live HTML or JavaScript, potentially leading to stored XSS.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.