CVE-2026-5751: EmilStenstrom justhtml · Cross-site Scripting
Affects EmilStenstrom justhtmlSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.14.0 when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.14.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Aug 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 21 Nov 2026.
What to do
Upgrade EmilStenstrom justhtml to 1.14.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EmilStenstromjusthtml | Affected
| Fixed in
|
GitHubemilstenstrom/justhtmlpkg:github/emilstenstrom/justhtmlOther 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
Upgrade justhtml to version 1.14.0 or later, where this vulnerability is fixed. Avoid using custom SanitizationPolicy configurations that preserve foreign namespaces unless necessary and ensure they are updated to the fixed version. The default configuration (sanitize=True) is not affected and does not require changes.
Description
justhtml versions 1.13.0 and earlier have a mutation cross-site scripting (mXSS) vulnerability when using a custom SanitizationPolicy that preserves foreign namespaces. This vulnerability allows specially crafted input to be sanitized into markup that appears safe but becomes unsafe when re-parsed by a browser or another HTML parser, enabling markup injection. The default safe configuration is not affected. The issue is fixed in version 1.14.0.