justhtml before 1.17.0 contains multiple security issues in sanitization, serialization, and programmatic DOM handling. When custom policies preserve foreign namespaces (SVG/MathML), dangerous content such as HTML integration points (SVG , MathML ) and mutation-XSS parser-differential payloads could survive sanitization and become active HTML after reparse; SVG filter="url(...)" and preserved could leave resource-loading CSS (@import, background-image:url()). Programmatic script/style/Comment nodes could serialize into active markup. Additional hardening fixes address sanitize-pipeline cache mutation and DOM parent/child cycles that could cause infinite loops. Most issues affect advanced or custom configurations rather than the default JustHTML(..., sanitize=True) safe path.
CVE-2026-6827
Score 6.1 from GitHub Security Advisory published 2026-08-23. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 23, 2026
Last Modified
August 26, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026justhtml before 1.17.0 Multiple Cross-Site Scripting Vulnerabilities | Advisories | VulnCheck
https://www.vulncheck.com/advisories/justhtml-before-multiple-cross-site-scripting-vulnerabilitiesMultiple security fixes in justhtml 1.16.0 found by LLM · Advisory · EmilStenstrom/justhtml · GitHub
https://github.com/EmilStenstrom/justhtml/security/advisories/GHSA-vrx2-77f2-ww34Vendor Advisories for CVE-2026-6827(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| justhtml | 0.1.0 ... 1.9.1 (61 versions) | 1.17.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 17:25 UTCEG score recompute
- 2026-08-26 17:25 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 16:36 UTCEG score recompute
- 2026-08-25 16:36 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 15:26 UTCEG score recompute
- 2026-08-24 15:26 UTCGHSA enrichment
- 2026-08-23 14:20 UTCEG score recompute
- 2026-08-23 13:51 UTCEG score recompute
- 2026-08-23 13:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-6827?
When was CVE-2026-6827 disclosed?
Is CVE-2026-6827 actively exploited?
What is the CVSS score of CVE-2026-6827?
How do I remediate CVE-2026-6827?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6827
Is Your Infrastructure Affected by CVE-2026-6827?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.