CVE-2024-45801

CVE-2024-45801 – DOMPurify prototype pollution/XSS issue : DOMPurify can bypass depth checks via special nesting and, separately, through prototype pollution weakening depth validation. The GHSA advisory details a prototype-pollution chain where Object.prototype.tagNameCheck and Object.prototype....

CVE-2025-15599

CVE-2025-15599 affects DOMPurify before and after versions 2.x and 3.x due to a missing textarea rawtext validation in SAFE_FOR_XML that allows bypassing attribute sanitization and executing JavaScript when sanitized output is placed inside rawtext elements. Affected ranges: 3.1.3–3.2.6 and 2.5.3...

CVE-2024-47875

CVE-2024-47875 affects DOMPurify and is a nesting-based mXSS vulnerability in DOMPurify’s HTML/MathML/SVG sanitization. The initial entry notes fixes in DOMPurify versions 2.5.0 and 3.1.3. Connected sources further confirm the issue is tracked across ecosystems (e.g., node-dompurify), with Debian...

CVE-2025-26791

DOMPurify is affected by an mXSS flaw in which an incorrect template-literal regular expression in versions before 3.2.4 can lead to mutation cross-site scripting. The CVE-2025-26791 entry is referenced across IBM notices for IBM Db2 Data Management Console, IBM Watson-related products, and other...

CVE-2024-48910

CVE-2024-48910 affects DOMPurify, a DOM-only XSS sanitizer. The vulnerability is a prototype pollution issue in DOMPurify that could enable remote code execution or similar impact as described in multiple sources. The fixed versions cited in the initial document include 2.4.2 for the DOMPurify is...

CVE-2020-26870

CVE-2020-26870 affects DOMPurify up to 2.0.16/2.0.17, where a serialize-parse roundtrip can alter the DOM (namespace changes HTML→MathML, e.g., nesting FORM elements), enabling a mutation XSS. The issue is documented by Cure53 and linked analyses; a fix was released with DOMPurify 2.0.17. Related...

CVE-2019-16728

Summary: CVE-2019-16728 affects DOMPurify prior to 2.0.1, enabling cross-site scripting via innerHTML mutation XSS (mXSS) in SVG or MATH elements, demonstrated in Chrome and Safari. Affected component: DOMPurify (HTML, MathML, SVG sanitization code). Root cause: improper handling of innerHTML mut...

CVE-2026-41240

Summary of technical details (CVE-2026-41240) : DOMPurify prior to 3.4.0 has an inconsistency between FORBID_TAGS and FORBID_ATTR when function-based ADD_TAGS is used. The fix added an early exit for FORBID_ATTR but the FORBID_TAGS path remained unpatched, causing short-circuiting that allows for...

CVE-2026-0540

CVE-2026-0540 affects DOMPurify versions 3.1.3–3.3.1 and 2.5.3–2.5.8. The vulnerability arises from five missing rawtext elements (noscript, xmp, noembed, noframes, iframe) in the SAFE_FOR_XML regex, allowing crafted attribute values to bypass sanitization and trigger XSS when output is placed in...

CVE-2026-49458

DOMPurify prior to v3.4.6 had a cross-realm IN_PLACE sanitization flaw where instanceof checks across realms allowed executable markup to bypass certain branches; fixed in v3.4.6. Affected: DOMPurify.sanitize with IN_PLACE in multi-realm scenarios. Mitigation: upgrade to DOMPurify 3.4.6 or later....

CVE-2026-49459

CVE-2026-49459 affects DOMPurify prior to 3.4.6, where IN_PLACE mode could retain event-handler attributes on an attacker‑controlled root DOM due to _isClobbered logic and incomplete removal paths. Affected component: DOMPurify.sanitize(root, { IN_PLACE: true }) with a clobbered root form. Conseq...

CVE-2026-47423

DOMPurify 3.4.4 contains a default allowlist misconfiguration that lets the selectedcontent element bypass sanitization by browser re-cloning after DOMPurify processes the subtree. This creates an XSS risk when attacker-controlled HTML is sanitized and then inserted (e.g., via innerHTML), since t...

CVE-2026-49978

CVE-2026-49978 affects DOMPurify, where IN_PLACE sanitization before version 3.4.7 could skip shadow contents inside a .content, allowing attacker-controlled markup (e.g., event handlers, JavaScript URLs, scripts) to survive during cloning and insertion of sanitized templates. The issue is fixed ...

CVE-2026-65898

DOMPurify before 3.4.11 is affected. The vulnerability arises when setConfig() is used with an uponSanitizeAttribute hook and the ALLOWED_ATTR allowlist isn’t cloned, allowing the hook to permanently mutate the shared allowlist. An attacker can register a hook that conditionally permits dangerous...

CVE-2019-25155

DOMPurify before 1.0.11 is affected by a reverse tabnabbing issue in demos/hooks-target-blank-demo.html due to missing rel="noopener noreferrer" on links. This is the concrete vulnerability described across CVE-2019-25155 entries: the root cause is the absence of a security attribute on target-bl...

CVE-2026-65903

DOMPurify before 3.4.0 contains a logic error in ADD_TAGS where short-circuit evaluation lets forbidden tags bypass FORBID_TAGS. Attackers can craft input containing tags listed in FORBID_TAGS that are also added via ADD_TAGS, causing those tags to be retained in the sanitized output. Affected: D...

CVE-2026-65913

DOMPurify prior to 3.3.2 is affected by a prototype pollution vulnerability in USE_PROFILES mode. An attacker can pollute Array.prototype properties (e.g., onclick) to bypass attribute filtering, causing DOMPurify to treat event handler attributes as allowed. This enables DOM-based XSS when sanit...

CVE-2026-65900

CVE-2026-65900 affects DOMPurify versions 3.0.0 up to 3.4.7 when configured with SAFE_FOR_TEMPLATES and a DOM output mode (RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE). The final scrub pass (_scrubTemplateExpressions) uses a NodeIterator and node.normalize() that do not descend into template.con...

CVE-2026-65901

DOMPurify 3.4.6 has a cross-site scripting vulnerability in IN_PLACE mode where attacker-controlled nodeName on live non-form nodes can cause scripts to execute when the sanitized tree is inserted into a live document. Attackers can supply hostile live DOM objects with real script children whose ...

CVE-2026-65914

DOMPurify contains a mutation-XSS in versions before 3.3.2 when sanitized HTML is reinserted into special parsing contexts via innerHTML wrappers (script, xmp, iframe, noembed, noframes, noscript). Attackers can craft payloads with closing sequences to break out of the wrapper during reparsing, r...

CVE-2026-65904

CVE-2026-65904 affects DOMPurify up to version 3.4.3. In IN_PLACE mode, elements sourced from a different window/realm (e.g., iframe contentDocument) fail sanitization due to a cross-realm instanceof check in private _isNode(). The check returns false for foreign-realm nodes, causing the element ...

CVE-2026-65911

CVE-2026-65911 concerns DOMPurify up to version 3.3.3. Predicates supplied via ADD_ATTR or ADD_TAGS to DOMPurify.sanitize() can persist in internal state (EXTRA_ELEMENT_HANDLING) across sanitize() calls on the same instance. If a subsequent call passes ADD_ATTR/ADD_TAGS as an array instead of a f...

CVE-2026-65899

The CVE affects DOMPurify 3.0.0 through 3.4.8, where clearConfig() does not reset the retained TRUSTED_TYPES_POLICY. This allows a DOMPurify instance reused across trust boundaries to remain bound to a previously supplied policy, so a later caller requesting RETURN_TRUSTED_TYPE output may receive...

CVE-2026-65902

DOMPurify 3.4.7 fixes a mutation pollution vulnerability. Affected: DOMPurify

CVE-2026-65912

DOMPurify before 3.3.2 has a URI validation bypass when ADD_ATTR is used as a predicate via EXTRA_ELEMENT_HANDLING.attributeCheck. An attacker can craft a predicate to accept specific attribute/tag combinations, allowing unsafe protocols like javascript: to bypass validation and execute as DOM-ba...