CVE-2026-109344 cure53 CVE debrief

Who should care

Defenders responsible for maintaining and securing web applications that utilize DOMPurify should be aware of this vulnerability and take steps to mitigate it. This includes verifying the versions of DOMPurify in use, updating to version 3.4.16 or later, and ensuring proper sanitization of user-supplied input.

Why it matters

CVE-2026-109344 is a cross-site scripting vulnerability in DOMPurify versions 3.4.13 to 3.4.15. Defenders should prioritize verifying DOMPurify versions, updating to 3.4.16 or later, and ensuring proper sanitization of user-supplied input to mitigate potential risks.

• Potential for attackers to inject malicious script
• Risk of cross-site scripting attacks
• Need for verification of DOMPurify versions and usage
• Importance of proper sanitization of user-supplied input

Technical summary

The vulnerability exists in DOMPurify versions 3.4.13 to 3.4.15, where the library's IN_PLACE mode fails to properly neutralize subtrees detached by afterSanitizeElements or afterSanitizeAttributes hooks. This allows attackers to inject malicious markup that can execute script in the victim's origin. Defenders should prioritize verifying the versions of DOMPurify in use within their environments and updating to version 3.4.16 or later. Additionally, reviewing and monitoring the usage of DOMPurify's IN_PLACE mode and ensuring proper sanitization of user-supplied input is crucial.

Defensive priority

Defenders should prioritize verifying the versions of DOMPurify in use within their environments and updating to version 3.4.16 or later. Additionally, reviewing and monitoring the usage of DOMPurify's IN_PLACE mode and ensuring proper sanitization of user-supplied input is crucial.

Recommended defensive actions

• Verify DOMPurify versions in use and update to 3.4.16 or later
• Review and monitor usage of DOMPurify's IN_PLACE mode
• Ensure proper sanitization of user-supplied input
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to vendor advisories. However, there is limited information on potential exploitation or specific attack scenarios.

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.