CVE-2026-49978 cure53 CVE debrief

Who should care

Developers and users of DOMPurify, especially those using versions prior to 3.4.7, should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and updating any affected applications or systems using DOMPurify, implementing additional security measures such as Content Security Policy (CSP) to mitigate XSS attacks, and verifying the vulnerability's impact on their systems.

Technical summary

DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Prior to 3.4.7, DOMPurify IN_PLACE sanitization could skip shadow contents attached to an element inside <template>.content, allowing attacker-controlled markup such as event handlers, JavaScript URLs, or scripts to survive and execute when an application cloned and inserted the sanitized template. This issue is fixed in version 3.4.7. The vulnerability has a CVSS score of 6.3 and is classified as MEDIUM severity. The fix involves updating the sanitizer to properly handle shadow contents attached to elements inside <template>.content.

Defensive priority

Medium priority given the CVSS score of 6.3 and the potential for XSS attacks.

Recommended defensive actions

• Upgrade to DOMPurify version 3.4.7 or later
• Review and update any affected applications or systems using DOMPurify
• Implement additional security measures such as Content Security Policy (CSP) to mitigate XSS attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD detail provide information on the vulnerability, its impact, and the fixed version. The vendor advisory and patch notes also provide additional context. Evidence limits suggest that further verification is needed to confirm affected scope and severity. Defenders should verify the vulnerability's impact on their systems and review the official advisory for guidance. The CVE record was published on 2026-07-14T21:17:02.560Z and has not been modified since then. Additional review of the sanitizer's functionality and potential weaknesses is recommended.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.