Quick answers
- Is CVE-2026-44990 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44990 being exploited in the wild.
- How severe is CVE-2026-44990?
- Critical severity, with a CVSS score of 9.3, published 12 June 2026.
- Which products and versions are affected?
- sanitize-html (npm) <= 2.17.3, = 2.17.3, SEMVER:introduced=2.17.3,fixed=2.17.4.
- Is there a fix for CVE-2026-44990?
- Yes. sanitize-html (npm): upgrade to 2.17.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44990 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44990?
- Check whether you run sanitize-html (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sanitize-html (npm): upgrade to 2.17.4 or later
npm install sanitize-html@2.17.4
Technical details
A cross-site scripting (XSS) vulnerability exists in sanitize-html prior to version 2.17.4 due to a sanitizer bypass in the default 'disallowedTagsMode: discard' configuration. The root cause is located in the ontext handler (index.js), which fails to escape text content within 'xmp' tags, appending it directly to the output. While htmlparser2 treats 'xmp' as raw text during input parsing, the library's failure to escape this content upon output allows nested tags (such as <script> or event handlers) to become live markup. An unauthenticated remote attacker can exploit this by submitting specially crafted HTML, leading to stored XSS when the sanitized output is rendered in a browser. The issue is resolved in version 2.17.4.
Affected products
- ApostropheCMS sanitize-html < 2.17.4
Identifiers
- CVE-2026-44990
- GHSA-rpr9-rxv7-x643
Timeline
- 2026-05-13: advisory: GitHub security advisory published by maintainers
- 2026-06-12: disclosed: NVD publication date
- 2026-06-12: patched: Version 2.17.4 released to address the bypass