# cure53/DOMPurify · Reposen Release & Migration Intelligence

> Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.

## Metadata
- **Repository URL**: https://github.com/cure53/DOMPurify
- **Primary Package**: `dompurify` (NPM)
- **Categories**: `ECOSYSTEM`, `STYLING`
- **Latest Version**: `v3.4.18`
- **Semantic Status**: `SECURITY_PATCH`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/cure53/DOMPurify/releases.atom

## The Human Context (Plain-English Pitch)
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.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.

## Breaking Changes & Required Actions
- Patched a security bypass in `SAFE_FOR_TEMPLATES` where 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_PROFILES` are specified alongside `ALLOWED_TAGS` or `ALLOWED_ATTR`.

## Migration Snippet
```ts
npm install dompurify@3.4.18
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **Node.js >=18** [`COMPATIBLE`]: Fully compatible with Node.js environments when paired with jsdom or happy-dom window shims.
- **TypeScript >=4.5** [`COMPATIBLE`]: Maintains native TypeScript ambient type definitions without signature changes.

## Zero-Noise Release Timeline
- **v3.4.18** (2026-11-14) [SECURITY_PATCH]: Fixes template bypass and clobbering check in sanitization. Upgrade dependency immediately. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is 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
