DOMPurify versions >=3.0.0 and before 3.4.8, when configured with SAFE_FOR_TEMPLATES together with a DOM output mode (RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE), fail to strip template expressions (e.g. ${evil}, {{evil}}, <%evil%>) inside <template> element content. The final normalization/scrub pass (_scrubTemplateExpressions) uses a NodeIterator and node.normalize() that do not descend into template.content, so expressions that only form after adjacent text nodes merge survive sanitization. This bypasses SAFE_FOR_TEMPLATES and can allow a downstream template engine to evaluate attacker-supplied expressions. The string output path is not affected.
References
| Link | Resource |
|---|---|
| https://github.com/cure53/DOMPurify/security/advisories/GHSA-gvmj-g25r-r7wr | Exploit Third Party Advisory |
| https://www.vulncheck.com/advisories/dompurify-before-template-expression-injection-via-return-dom | Third Party Advisory |
| https://github.com/cure53/DOMPurify/security/advisories/GHSA-gvmj-g25r-r7wr | Exploit Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-07-23 14:18
Updated : 2026-07-28 15:52
NVD link : CVE-2026-65900
Mitre link : CVE-2026-65900
CVE.ORG link : CVE-2026-65900
JSON object : View
Products Affected
cure53
- dompurify
CWE
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
