Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-44990: Stored XSS via disallowed xmp elements in sanitize-html

Published Jun 12, 2026 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.1High · v3.1
EPSS0.68%53rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-44990CWE-79 · Improper Neutralization of Input…

CVE-2026-44990 is a sanitizer bypass in sanitize-html, an HTML sanitization library used by ApostropheCMS and other applications. In the default disallowedTagsMode: 'discard' code path, attacker-controlled content within a disallowed xmp element can be emitted unescaped and interpreted as active HTML or JavaScript. Applications that store and subsequently render this output as trusted HTML can expose users to stored cross-site scripting. Version 2.17.4 fixes the vulnerability. The published affected range is versions before 2.17.4, although an unconfirmed report questions whether the flaw was introduced specifically in 2.17.3.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation executes attacker-controlled JavaScript in a victim's browser within the affected application's origin. This can compromise application data confidentiality and integrity, including reading data accessible to the victim and performing application actions with the victim's privileges. The demonstrated vulnerability is browser-side cross-site scripting, not server-side code execution.

Mitigation

If you can’t patch tonight, do this now.

Until patched, reject untrusted HTML containing xmp elements or use robust preprocessing that removes those elements together with their contents. Configure sanitization to discard dangerous raw-text containers completely rather than preserving their contents. Where HTML rendering is unnecessary, render untrusted content as text using appropriate output encoding instead of treating sanitized output as trusted HTML.

Remediation

Patch, then assume compromise.

Upgrade sanitize-html to version 2.17.4 or later. For applications that bundle the library, install the corresponding vendor security update and verify that the deployed dependency has been replaced. Do not assume versions earlier than 2.17.3 are unaffected without authoritative confirmation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-44990 exploited in the wild?
As of Oct 21, 2026, Mallory has no reports of CVE-2026-44990 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-44990?
Yes. As of Oct 21, 2026, Mallory has reports of a public exploit for CVE-2026-44990.
Is there a patch for CVE-2026-44990?
Upgrade sanitize-html to version 2.17.4 or later. For applications that bundle the library, install the corresponding vendor security update and verify that the deployed dependency has been replaced.
How severe is CVE-2026-44990?
CVE-2026-44990 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.68% (53rd percentile) as of Oct 21, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.