build(deps): bump dompurify from 3.3.2 to 3.4.0

[dependabot]

Bumps dompurify from 3.3.2 to 3.4.0.

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.0

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

DOMPurify 3.3.3

• Fixed an engine requirement for Node 20 which caused hiccups, thanks @​Rotzbua

Commits

• 5b16e0b Getting 3.x branch ready for 3.4.0 release (#1250)
• 8bcbf73 chore: Preparing 3.3.3 release
• 5faddd6 fix: engine requirement (#1210)
• 0f91e3a Update README.md
• d5ff1a8 Merge branch 'main' of github.com:cure53/DOMPurify
• c3efd48 fix: moved back from jsdom 28 to jsdom 20
• 988b888 fix: moved back from jsdom 28 to jsdom 20
• 2726c74 chore: Preparing 3.3.2 release
• 6202c7e build(deps): bump @​tootallnate/once and jsdom (#1204)
• 302b51d fix: Expanded the regex ever so slightly to also cover script
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[greptile-apps]

Greptile Summary

Bumps dompurify from 3.3.2 to 3.4.0. This is a security-relevant update that patches prototype pollution via CUSTOM_ELEMENT_HANDLING and USE_PROFILES, two mXSS vectors (re-contextualization and malformed closing tags), and ADD_ATTR predicates bypassing URI validation. The lock file change also removes the previously incorrect engines: { node: ">=20" } constraint (corrected in 3.3.3).

Confidence Score: 5/5

Safe to merge — clean security patch with no API or behavioral breaking changes

Pure dependency bump with only version and integrity hash changes. DOMPurify 3.4.0 is a minor version that resolves multiple security vulnerabilities without breaking the public API. No application code is touched.

No files require special attention

Important Files Changed

Filename	Overview
package.json	dompurify version constraint bumped from ^3.3.2 to ^3.4.0 — straightforward, no other changes
package-lock.json	Lock file updated to dompurify 3.4.0 with new integrity hash; engines node>=20 constraint removed (fixed in 3.3.3 per changelog)

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[package.json / package-lock.json] -->|dompurify ^3.3.2 → ^3.4.0| B[DOMPurify 3.4.0]
    B --> C[Fixes: prototype pollution\nCUSTOM_ELEMENT_HANDLING, USE_PROFILES]
    B --> D[Fixes: mXSS via\nre-contextualization & closing tags]
    B --> E[Fixes: ADD_ATTR predicates\nskipping URI validation]
    B --> F[Removes incorrect\nnode>=20 engines constraint]

Loading

_{Reviews (1): Last reviewed commit: "build(deps): bump dompurify from 3.3.2 t..." | Re-trigger Greptile}