[From nobody Tue Oct 27 20:01:13 2026
Received: (at submit) by bugs.debian.org; 27 Oct 2026 18:23:44 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-107.1 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
 FOURLA,FROMDEVELOPER,SPF_HELO_NONE,SPF_PASS,USER_IN_DKIM_WELCOMELIST
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 149; neutral, 74; spammy,
 1. spammytokens:0.977-+--click
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;carnil@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:35974)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xLlpo-00C9xN-1y
 for submit@bugs.debian.org; Tue, 27 Oct 2026 18:23:44 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=xonDbZWP94+8mv6GYxRmo3QZ51ZWo8BRwhdhUA2EBig=; b=cV0TYsPB2mFY3Xedk7c7SgM0Qx
 Bevzf497f5poc+t0GyerbSqfbNVe4O2aL/4EzgMWyWCsmGgRUyCN/NWpoeB4v25Fcr8sFEpXam4Yw
 oTmxyYMLbtjYge8mt+RCRdPYM6SXagUtWlM40uO9MOJ0r4XlyEQGYr0GY3XZwbGDe2xjxS97rSou3
 UXwRO+DJJXDnNWRJN6HV8UBqeZ/vY+Fj1U+d0J3LA4u5NDMixQJQkOLUtLQGnfwZHJNfNfhyR+HyE
 fWxwohBpI0b5UxRU2yRuvw86h/8dWZGcJsmh3kmdTuvl87vUsKhO6zPoLdlyFwQyQOYprgv39q/E+
 ISHxwVkg==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;carnil@debian.org&gt;) id 1xLlpk-001eMY-1q
 for submit@bugs.debian.org; Tue, 27 Oct 2026 18:23:42 +0000
Received: by eldamar.lan (Postfix, from userid 1000)
 id 78BA6DC03F0; Tue, 27 Oct 2026 19:23:39 +0100 (CET)
Date: Tue, 27 Oct 2026 19:23:39 +0100
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: submit@bugs.debian.org
Subject: node-dompurify: CVE-2026-116802 CVE-2026-116803 CVE-2026-116804
Message-ID: &lt;auDsK7KwLGnBUsFs@eldamar.lan&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: carnil
Delivered-To: submit@bugs.debian.org

Source: node-dompurify
Version: 3.4.16+dfsg-1
X-Debbugs-CC: team@security.debian.org
Severity: important
Tags: security upstream

Hi,

The following vulnerabilities were published for node-dompurify.

CVE-2026-116802[0]:
| DOMPurify before 3.4.17 contains a cross-site scripting
| vulnerability that allows attackers to bypass the SMIL
| attributeName=href guard when PARSER_MEDIA_TYPE is
| application/xhtml+xml, because transformCaseFunc does not lowercase
| attribute names. Attackers can submit SVG with an animate or set
| element using attributeName=&quot;href&quot; and a javascript: entry in values
| to execute script when users click the sanitized link.


CVE-2026-116803[1]:
| DOMPurify before 3.4.17 contains a cross-site scripting
| vulnerability that allows attackers to keep event handlers armed
| when an IN_PLACE hook removes a parent or sibling node. Attacker
| markup in detached subtrees is never walked or neutralized, so
| handlers like img onerror fire after sanitize() returns, causing DOM
| XSS.


CVE-2026-116804[2]:
| DOMPurify from 3.4.4 before 3.4.17 contains a SAFE_FOR_TEMPLATES
| bypass that lets attackers preserve template expressions in attached
| shadow roots when using RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE
| modes. Attackers can split expressions across text nodes separated
| by disallowed elements, which merge after removal and are evaluated
| by downstream template engines for cross-site scripting.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-116802
    https://www.cve.org/CVERecord?id=CVE-2026-116802
[1] https://security-tracker.debian.org/tracker/CVE-2026-116803
    https://www.cve.org/CVERecord?id=CVE-2026-116803
[2] https://security-tracker.debian.org/tracker/CVE-2026-116804
    https://www.cve.org/CVERecord?id=CVE-2026-116804

Regards,
Salvatore
]