Skip to content

Bump dompurify from 3.3.3 to 3.4.11#351

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dompurify-3.4.11
Open

Bump dompurify from 3.3.3 to 3.4.11#351
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dompurify-3.4.11

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 17, 2026

Copy link
Copy Markdown
Contributor

Bumps dompurify from 3.3.3 to 3.4.11.

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.11

  • Fixed an issue with a leaky config for hooks via setConfig, thanks @​trace37labs
  • Bumped vulnerable development dependencies to arrive at plain 0 with npm audit
  • Updated the osv-scanner suppression list as no vulnerable dependencies are left for now
  • Updated up the linting tool-chain and removed now-redundant lint directives
  • Updated the documentation is several spots, README, wiki, etc.
  • Bumped several dependencies where possible

DOMPurify 3.4.10

  • Refactored codebase for clarity: extracted the public type declarations into types.ts
  • Decomposed the three largest sanitizer functions into focused helpers
  • Removed duplicated defaults and dead branches, consolidated SAFE_FOR_TEMPLATES scrubbing into single shared path
  • Improved per-node performance by hoisting the mXSS probe regexes and testing textContent before innerHTML
  • Added a deterministic micro-benchmark harness (npm run bench) with a --compare mode
  • Reduced CI cost by running the full three-engine browser suite once per PR
  • Refreshed the demos/ folder so every demo runs again, and added a SVG-via-<img> demo
  • Documented the bench and test:happydom scripts in the README
  • Completed the Attack Classes & Bypass History wiki page
  • Bumped several dependencies where possible

DOMPurify 3.4.9

  • Further improved the handling of Trusted Types config options, thanks @​offset
  • Further improved the handling of IN_PLACE sanitization, thanks @​mozfreddyb
  • Added more test coverage for IN_PLACE and Trusted Types related usage
  • Bumped several dependencies where possible
  • Updated README and wiki with more accurate documentation & attack samples

DOMPurify 3.4.8

  • Cleaned up the repository root, renamed some and removed unneeded files
  • Fixed an issue with handling of Trusted Types policies, thanks @​fulstadev
  • Fixed the node iterator for better template scrubbing, thanks @​IamLeandrooooo
  • Included formerly missing LICENSE-MPL in published npm package, thanks @​asamuzaK
  • Bumped several dependencies where possible

DOMPurify 3.4.7

  • Hardened the handling of Shadow Roots when using IN_PLACE, thanks @​GameZoneHacker
  • Removed a problem leading to permanent hook pollution, thanks @​offset
  • Refactored the test suite and expanded test coverage significantly

DOMPurify 3.4.6

  • Fixed several issues with DOM Clobbering in IN_PLACE mode, thanks @​offset & @​Bankde
  • Hardened the checks for cross-realm IN_PLACE and Shadow DOM sanitization, thanks @​offset & @​Bankde
  • Added more test coverage for IN_PLACE and general DOM Clobbering attacks
  • Bumped several dependencies where possible

DOMPurify 3.4.5

  • Fixed a bypass caused by the new HTML element selectedcontent added in 3.4.4, thanks @​KabirAcharya

Note that this is a security release for an issue introduced in 3.4.4 and should be upgraded to immediately.

... (truncated)

Commits
Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Dependabot compatibility score

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.

Bumps [dompurify](https://github.com/cure53/DOMPurify) from 3.3.3 to 3.4.11.
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](cure53/DOMPurify@3.3.3...3.4.11)

---
updated-dependencies:
- dependency-name: dompurify
  dependency-version: 3.4.11
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 17, 2026
@dependabot dependabot Bot requested a review from a team as a code owner June 17, 2026 22:07
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 17, 2026
@github-actions

Copy link
Copy Markdown

MegaLinter analysis: Error

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 4 0 0 0.06s
❌ ACTION zizmor 4 1 0 0.4s
✅ JSON jsonlint 6 0 0 0.11s
✅ JSON prettier 6 0 0 0.93s
✅ JSON v8r 6 0 0 6.5s
✅ MARKDOWN markdownlint 5 0 0 0.61s
✅ REPOSITORY checkov yes no no 23.22s
✅ REPOSITORY gitleaks yes no no 7.12s
✅ REPOSITORY git_diff yes no no 0.02s
❌ REPOSITORY osv-scanner yes 39 no 2.95s
✅ REPOSITORY secretlint yes no no 1.2s
✅ REPOSITORY syft yes no no 7.34s
✅ REPOSITORY trivy-sbom yes no no 11.18s
❌ TSX eslint 47 1 0 0.58s
❌ TYPESCRIPT eslint 2 1 0 1.09s
✅ TYPESCRIPT prettier 2 0 0 2.03s
✅ YAML prettier 9 0 0 0.66s
✅ YAML v8r 9 0 0 5.92s
✅ YAML yamllint 9 0 0 0.69s

Detailed Issues

❌ TSX / eslint - 1 error
Oops! Something went wrong! :(

ESLint: 10.3.0

Error: Cannot read config file: node_modules/eslint-config-next/index.js
Error: Failed to patch ESLint because the calling module was not recognized.
If you are using a newer ESLint version that may be unsupported, please create a GitHub issue:
https://github.com/microsoft/rushstack/issues
Referenced from: node_modules/eslint-config-next/core-web-vitals.js
    at Object.<anonymous> (node_modules/@rushstack/eslint-patch/lib/_patch-base.js:167:19)
    at Module._compile (node:internal/modules/cjs/loader:1760:14)
    at Object..js (node:internal/modules/cjs/loader:1893:10)
    at Module.load (node:internal/modules/cjs/loader:1480:32)
    at Module._load (node:internal/modules/cjs/loader:1299:12)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)
    at Module.require (node:internal/modules/cjs/loader:1503:12)
    at require (node:internal/modules/helpers:152:16)
    at Object.<anonymous> (node_modules/@rushstack/eslint-patch/lib/modern-module-resolution.js:11:23)
❌ TYPESCRIPT / eslint - 1 error
Oops! Something went wrong! :(

ESLint: 10.3.0

Error: Cannot read config file: node_modules/eslint-config-next/index.js
Error: Failed to patch ESLint because the calling module was not recognized.
If you are using a newer ESLint version that may be unsupported, please create a GitHub issue:
https://github.com/microsoft/rushstack/issues
Referenced from: node_modules/eslint-config-next/core-web-vitals.js
    at Object.<anonymous> (node_modules/@rushstack/eslint-patch/lib/_patch-base.js:167:19)
    at Module._compile (node:internal/modules/cjs/loader:1760:14)
    at Object..js (node:internal/modules/cjs/loader:1893:10)
    at Module.load (node:internal/modules/cjs/loader:1480:32)
    at Module._load (node:internal/modules/cjs/loader:1299:12)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)
    at Module.require (node:internal/modules/cjs/loader:1503:12)
    at require (node:internal/modules/helpers:152:16)
    at Object.<anonymous> (node_modules/@rushstack/eslint-patch/lib/modern-module-resolution.js:11:23)
❌ REPOSITORY / osv-scanner - 39 errors
Scanning dir .
Starting filesystem walk for root: /
Scanned package-lock.json file and found 723 packages
End status: 58 dirs visited, 189 inodes visited, 1 Extract calls, 32.660887ms elapsed, 32.661169ms wall time

Total 15 packages affected by 39 known vulnerabilities (0 Critical, 15 High, 21 Medium, 3 Low, 0 Unknown) from 1 ecosystem.
39 vulnerabilities can be fixed.

+-------------------------------------+------+-----------+-----------------------+---------+---------------+-------------------+
| OSV URL                             | CVSS | ECOSYSTEM | PACKAGE               | VERSION | FIXED VERSION | SOURCE            |
+-------------------------------------+------+-----------+-----------------------+---------+---------------+-------------------+
| https://osv.dev/GHSA-4x5r-pxfx-6jf8 | 3.2  | npm       | @babel/core           | 7.26.9  | 7.29.6        | package-lock.json |
| https://osv.dev/GHSA-f886-m6hf-6m8v | 6.5  | npm       | brace-expansion (dev) | 1.1.12  | 1.1.13        | package-lock.json |
| https://osv.dev/GHSA-f886-m6hf-6m8v | 6.5  | npm       | brace-expansion (dev) | 2.0.2   | 2.0.3         | package-lock.json |
| https://osv.dev/GHSA-25h7-pfq9-p65f | 7.5  | npm       | flatted (dev)         | 3.3.3   | 3.4.0         | package-lock.json |
| https://osv.dev/GHSA-rf6f-7fwh-wjgh | 8.9  | npm       | flatted (dev)         | 3.3.3   | 3.4.2         | package-lock.json |
| https://osv.dev/GHSA-h67p-54hq-rp68 | 5.3  | npm       | js-yaml (dev)         | 4.1.1   | 4.2.0         | package-lock.json |
| https://osv.dev/GHSA-f23m-r3pf-42rh | 6.5  | npm       | lodash                | 4.17.23 | 4.18.0        | package-lock.json |
| https://osv.dev/GHSA-r5fr-rjxr-66jc | 8.1  | npm       | lodash                | 4.17.23 | 4.18.0        | package-lock.json |
| https://osv.dev/GHSA-f23m-r3pf-42rh | 6.5  | npm       | lodash-es             | 4.17.21 | 4.18.0        | package-lock.json |
| https://osv.dev/GHSA-r5fr-rjxr-66jc | 8.1  | npm       | lodash-es             | 4.17.21 | 4.18.0        | package-lock.json |
| https://osv.dev/GHSA-xxjr-mmjv-4gpg | 6.9  | npm       | lodash-es             | 4.17.21 | 4.17.23       | package-lock.json |
| https://osv.dev/GHSA-6m6c-36f7-fhxh | 5.3  | npm       | mermaid               | 11.12.2 | 11.15.0       | package-lock.json |
| https://osv.dev/GHSA-87f9-hvmw-gh4p | 5.3  | npm       | mermaid               | 11.12.2 | 11.15.0       | package-lock.json |
| https://osv.dev/GHSA-ghcm-xqfw-q4vr | 5.3  | npm       | mermaid               | 11.12.2 | 11.15.0       | package-lock.json |
| https://osv.dev/GHSA-xcj9-5m2h-648r | 5.3  | npm       | mermaid               | 11.12.2 | 11.15.0       | package-lock.json |
| https://osv.dev/GHSA-267c-6grr-h53f | 7.5  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-26hh-7cqf-hhc6 | 7.5  | npm       | next                  | 15.5.10 | 15.5.18       | package-lock.json |
| https://osv.dev/GHSA-36qx-fr4f-26g5 | 7.5  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-3g8h-86w9-wvmq | 3.7  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-3x4c-7xq6-9pq8 | 6.9  | npm       | next                  | 15.5.10 | 15.5.14       | package-lock.json |
| https://osv.dev/GHSA-492v-c6pp-mqqv | 8.1  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-8h8q-6873-q5fj | 7.5  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-c4j6-fc7j-m34r | 8.6  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-ffhc-5mcf-pf4q | 4.7  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-ggv3-7p47-pfv8 | 6.3  | npm       | next                  | 15.5.10 | 15.5.13       | package-lock.json |
| https://osv.dev/GHSA-gx5p-jg67-6x7h | 6.1  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-h64f-5h5j-jqjh | 5.9  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-mg66-mrh9-m8jx | 7.5  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-q4gf-8mx6-v5v3 | 7.5  | npm       | next                  | 15.5.10 | 15.5.15       | package-lock.json |
| https://osv.dev/GHSA-vfv6-92ff-j949 | 3.7  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-wfc6-r584-vfw7 | 5.4  | npm       | next                  | 15.5.10 | 15.5.16       | package-lock.json |
| https://osv.dev/GHSA-3v7f-55p6-f55p | 5.3  | npm       | picomatch             | 2.3.1   | 2.3.2         | package-lock.json |
| https://osv.dev/GHSA-c2c7-rcm5-vvqj | 7.5  | npm       | picomatch             | 2.3.1   | 2.3.2         | package-lock.json |
| https://osv.dev/GHSA-3v7f-55p6-f55p | 5.3  | npm       | picomatch (dev)       | 4.0.2   | 4.0.4         | package-lock.json |
| https://osv.dev/GHSA-c2c7-rcm5-vvqj | 7.5  | npm       | picomatch (dev)       | 4.0.2   | 4.0.4         | package-lock.json |
| https://osv.dev/GHSA-qx2v-qp2m-jg93 | 6.1  | npm       | postcss               | 8.4.31  | 8.5.10        | package-lock.json |
| https://osv.dev/GHSA-qx2v-qp2m-jg93 | 6.1  | npm       | postcss (dev)         | 8.5.8   | 8.5.10        | package-lock.json |
| https://osv.dev/GHSA-w5hq-g745-h8pq | 7.5  | npm       | uuid                  | 11.1.0  | 11.1.1        | package-lock.json |
| https://osv.dev/GHSA-48c2-rrv3-qjmp | 4.3  | npm       | yaml                  | 1.10.2  | 1.10.3        | package-lock.json |
+-------------------------------------+------+-----------+-----------------------+---------+---------------+-------------------+
❌ ACTION / zizmor - 1 error
INFO zizmor: 🌈 zizmor v1.25.0
fatal: no audit was performed
'ref-confusion' audit failed on file://.github/workflows/codeql.yml

Caused by:
    0: error in 'ref-confusion' audit
    1: couldn't list branches for actions/checkout
    2: request error while accessing GitHub API
    3: HTTP status client error (401 Unauthorized) for url (https://github.com/actions/checkout.git/git-upload-pack)


[ZizmorLinter] Zizmor failed to reach the GitHub API.
To allow zizmor to use GITHUB_TOKEN, add the following to your .mega-linter.yml:
ACTION_ZIZMOR_UNSECURED_ENV_VARIABLES:
  - GITHUB_TOKEN

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.5.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,TSX_ESLINT,TYPESCRIPT_ES,TYPESCRIPT_PRETTIER,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants