[Snyk] Upgrade dompurify from 3.4.0 to 3.4.1

[Mpdreamz]

Snyk has created this PR to upgrade dompurify from 3.4.0 to 3.4.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released 22 days ago.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Release notes

Package name: dompurify

• 3.4.1 - 2026-04-21
  
  • Fixed an issue with on-handler stripping for HTML-spec-reserved custom element names (font-face, color-profile, missing-glyph, font-face-src, font-face-uri, font-face-format, font-face-name) under permissive CUSTOM_ELEMENT_HANDLING
  • Fixed a case-sensitivity gap in the annotation-xml check that allowed mixed-case variants to bypass the basic-custom-element exclusion in XHTML mode
  • Fixed SANITIZE_NAMED_PROPS repeatedly prefixing already-prefixed id and name values on subsequent sanitization
  • Fixed the IN_PLACE root-node check to explicitly guard against non-string nodeName (DOM-clobbering robustness)
  • Removed a duplicate slot entry from the default HTML attribute allow-list
  • Strengthened the fast-check fuzz harness with explicit XSS invariants, an expanded seed-payload corpus, an additional idempotence property for SANITIZE_NAMED_PROPS, and a negative-control assertion ensuring the invariants actually fire
  • Added regression and pinning tests covering the above fixes and two accepted-behavior contracts (SAFE_FOR_TEMPLATES greedy scrub, hook-added attribute handling)
  • Extended CodeQL analysis to run on 3.x and 2.x maintenance branches
• 3.4.0 - 2026-04-14
  

  Most relevant changes:

  • Fixed a problem with FORBID_TAGS not winning over ADD_TAGS, thanks @ kodareef5
  • Fixed several minor problems and typos regarding MathML attributes, thanks @ DavidOliver
  • Fixed ADD_ATTR/ADD_TAGS function leaking into subsequent array-based calls, thanks @ 1Jesper1
  • Fixed a missing SAFE_FOR_TEMPLATES scrub in RETURN_DOM path, thanks @ bencalif
  • Fixed a prototype pollution via CUSTOM_ELEMENT_HANDLING, thanks @ trace37labs
  • Fixed an issue with ADD_TAGS function form bypassing FORBID_TAGS, thanks @ eddieran
  • Fixed an issue with ADD_ATTR predicates skipping URI validation, thanks @ christos-eth
  • Fixed an issue with USE_PROFILES prototype pollution, thanks @ christos-eth
  • Fixed an issue leading to possible mXSS via Re-Contextualization, thanks @ researchatfluidattacks and others
  • Fixed an issue with closing tags leading to possible mXSS, thanks @ frevadiscor
  • Fixed a problem with the type dentition patcher after Node version bump
  • Fixed freezing BS runs by reducing the tested browsers array
  • Bumped several dependencies where possible
  • Added needed files for OpenSSF scorecard checks

  Published Advisories are here:
  https://github.com/cure53/DOMPurify/security/advisories?state=published

from dompurify GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[Mpdreamz]

This is a patch version upgrade that includes several bug fixes and security hardenings. According to the release notes, the changes address edge cases and do not introduce any breaking API changes. No developer action is required for this upgrade.

Fixes include:

• Corrected on-handler stripping for certain custom element names.
• Fixed a case-sensitivity issue in the annotation-xml check.
• Prevented repeated prefixing of id and name values by SANITIZE_NAMED_PROPS.

Source: GitHub Releases

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.