cure53/DOMPurify
v3.4.18Curated ecosystem / styling repository (cure53/DOMPurify) tracked via conditional GitHub .atom polling.
DOMPurify is an ultra-fast, robust HTML sanitizer designed for browser and Node.js environments. When applications inject untrusted user input into the DOM, they are susceptible to Cross-Site Scripting (XSS) attacks. DOMPurify parses, scrubs, and neutralizes malicious tags and attributes, ensuring that rendered HTML output remains safe without altering clean styling or markup.
Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.
Key Release Highlights (v3.4.18)
- Patched a security bypass in
SAFE_FOR_TEMPLATESwhere tag truncation during final scrubbing permitted template expression reconstruction on reparse. - Resolved a DOM clobbering vulnerability triggered by a direct property read during clobbering validation passes.
- Cleaned SVG allowlists by pruning attribute names mistakenly categorized as SVG element tags.
- Added diagnostic console warnings when conflicting
USE_PROFILESare specified alongsideALLOWED_TAGSorALLOWED_ATTR.
Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.
npm install dompurify@3.4.18Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.
Upgrade & Migration Q&A (cure53/DOMPurify v3.4.18)
Direct Answers for Engineers & AI AgentsIs cure53/DOMPurify v3.4.18 safe to upgrade in production?
cure53/DOMPurify v3.4.18 is classified as SECURITY_PATCH (PATCH release). Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.
What breaking changes or compatibility risks exist in cure53/DOMPurify v3.4.18?
No breaking API changes or peer dependency conflicts are recorded for cure53/DOMPurify v3.4.18 in the Reposen compatibility graph.
What is the bundle size impact of dompurify v3.4.18?
Measured bundle size telemetry is currently unavailable for dompurify v3.4.18; verify build output locally before deploying.
How do I upgrade dompurify to v3.4.18?
Upgrade dompurify to v3.4.18 by running "npm install dompurify@3.4.18" and applying the migration steps: npm install dompurify@3.4.18
Featured in Daily Cortex Briefs (1)
Browse All Daily Briefs →yjs/yjs (v14.0.0-rc.30) & cure53/DOMPurify (v3.4.18) — State, Data & UI Evolution
Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.