Cross-site scripting via recombined template expressions
Published Apr 23, 2026 · Updated Apr 23, 2026
Cross-site scripting in Cure53 DOMPurify 1.0.10 through 3.3.3 allows remote attackers to execute script through crafted HTML. The RETURN_DOM branch exits before the final serialized-output scrub; after disallowed elements are removed, adjacent text nodes recombine into a template expression. Exploitation requires a DOM-return option, SAFE_FOR_TEMPLATES, a template-evaluating framework, and user rendering of attacker-controlled content.
Summary
What happened
Cross-site scripting in Cure53 DOMPurify 1.0.10 through 3.3.3 allows remote attackers to execute script through crafted HTML. The RETURN_DOM branch exits before the final serialized-output scrub; after disallowed elements are removed, adjacent text nodes recombine into a template expression. Exploitation requires a DOM-return option, SAFE_FOR_TEMPLATES, a template-evaluating framework, and user rendering of attacker-controlled content.
The record
- CVE
- CVE-2026-41239
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- Cure53
- Product
- DOMPurify
- Classifications
- CWE-79, CWE-1289, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.0.10, < 3.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream SAFE_FOR_TEMPLATES browser reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo