vulns.co
/
GKData.io MCP and API Buy me a coffee

DOMPurify / Cure53

DOMPurify: accepted DOM realms must retain complete sanitization

DOMPurify could accept DOM objects from another JavaScript realm but fail to recognize them during later sanitization. Its CVE-2026-49458 advisory describes local-constructor checks that could skip protections and leave nested content unchecked. The lesson is that every accepted kind of input needs the full set of security checks.

Open the referenceMaintainer AdvisoryReviewed 2026-10-04

How to use this reference

Compare the set of accepted representations with the set covered by every protective decision, including nested content. Treat an unrecognized representation as an explicit policy decision rather than silently skipping validation. Review remediation and regression coverage together. These are conceptual review objectives, not a claim that any specific proposed implementation was shipped or independently tested.

Before reading

  • JavaScript realm and DOM object concepts
  • Sanitization, nested content and browser activation boundaries

Context and limits

  • The advisory requires attacker-influenced DOM from another same-origin realm, in-place sanitization and subsequent consumer activation. It excludes ordinary string input and same-realm in-place use from this issue.
  • It reports script execution with Chromium 148 and DOMPurify 3.4.5. Production compromise, account takeover and independent reproduction are not established here.
  • The advisory lists versions through 3.4.5 as affected and 3.4.6 as patched. This historical minimum is not a comprehensive current security guarantee.
  • The official 3.4.6 release describes stronger cross-realm and shadow-DOM checks plus expanded regression coverage. Its metadata records May 26, 2026 at 13:04:11 UTC; that software-release time is separate from the unknown resource-edition date. Advisory suggestions are not evidence of exact shipped implementation.
  • The advisory credits offset as Reporter. cure53 is the publishing account, not an explicit article byline, so authors remains empty. Release-wide thanks to offset and Bankde do not establish both as reporters of this particular advisory.

Sources

  1. Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound instanceof checksDOMPurify / Cure53 · reviewed 2026-10-04
  2. DOMPurify 3.4.6DOMPurify / Cure53 · reviewed 2026-10-04
  3. Official DOMPurify 3.4.6 release metadataDOMPurify / Cure53 via GitHub · reviewed 2026-10-04

Record reviewed 2026-10-04. Snapshot a066321c166a. Open the complete JSON contract.

Library synced 2026-11-19 · cases last reviewed 2026-10-05

a066321c166a · JSON exports & schemas · CC BY 4.0 content / MIT software