Bump dompurify and swagger-ui-react

[dependabot]

Bumps dompurify to 3.4.11 and updates ancestor dependency swagger-ui-react. These dependencies need to be updated together.

Updates dompurify from 3.2.6 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

• 0cae518 release: 3.4.11 (#1494)
• 6ee5716 release: 3.4.10 (#1478)
• 5210247 release: 3.4.9 (#1459)
• bcdd828 release: 3.4.8 (#1439)
• ca30f07 release: 3.4.7 (#1414)
• bb7739e release: 3.4.6 (#1394)
• 011b0c7 release: 3.4.5 (#1382)
• 5817ad9 release: 3.4.4 (#1374)
• 520edb0 release: 3.4.3 (#1352)
• 6f67fd3 Sync/3.4.2 (#1322)
• Additional commits viewable in compare view

Install script changes

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

Updates swagger-ui-react from 5.31.0 to 5.32.8

Release notes

Sourced from swagger-ui-react's releases.

v5.32.8

5.32.8 (2026-06-23)

Bug Fixes

• avoid filling parameter input with invalid array initial values (#10928) (014c512)

v5.32.7

5.32.7 (2026-06-22)

Bug Fixes

• deps: bump dompurify from 3.4.0 to 3.4.9 (#10923) (15fc7d1)
• deps: bump dompurify from 3.4.9 to 3.4.11 (#10931) (52ef1c9)
• deps: bump form-data from 4.0.5 to 4.0.6 (#10924) (f8bcbbf)
• deps: bump http-proxy-middleware to 2.0.10 and ws to 8.21.0 (#10935) (dd0d338)
• deps: bump js-yaml from 4.1.1 to 4.2.0 (#10927) (bf17869)
• deps: bump launch-editor from 2.10.0 to 2.14.1 (#10926) (9b6b6ff)

v5.32.6

5.32.6 (2026-05-12)

Bug Fixes

• deps-dev: address undici vulnerability (#10870) (35f5a6a)
• docker: address CVE-2026-27135 nghttp2-libs vulnerability (#10879) (0a63415)

v5.32.5

5.32.5 (2026-04-27)

Bug Fixes

• deps: bump swagger-client to v3.37.3 (#10858) (74e48ce)
• style: markdown list items default text color in Dark Mode (#10790) (#10791) (3608eaa)

Reverts

• Revert "Accessibility: Easier to access Authorization (#10692)" (#10850) (8d17c78)

v5.32.4

5.32.4 (2026-04-15)

Bug Fixes

... (truncated)

Commits

• 4e0d3f8 chore(release): cut the 5.32.8 release
• b1990bf chore(deps): bump nginx from 1.31.0-alpine to 1.31.2-alpine (#10936)
• 014c512 fix: avoid filling parameter input with invalid array initial values (#10928)
• bf6a8f0 chore(release): cut the 5.32.7 release
• dd0d338 fix(deps): bump http-proxy-middleware to 2.0.10 and ws to 8.21.0 (#10935)
• 6287405 chore(deps): bump actions/checkout from 6 to 7 (#10933)
• 52ef1c9 fix(deps): bump dompurify from 3.4.9 to 3.4.11 (#10931)
• 4d21bfb chore(deps-dev): bump webpack-dev-server from 5.2.4 to 5.2.5 (#10930)
• fb2c061 chore(deps-dev): bump @​babel/core from 7.26.10 to 7.29.6 (#10925)
• f8bcbbf fix(deps): bump form-data from 4.0.5 to 4.0.6 (#10924)
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 26, 2026 1:31am

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	swagger-ui-react@​5.31.0 ⏵ 5.32.8				+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/swagger-ui-react@5.32.8 → npm/@docusaurus/theme-mermaid@3.9.2 → npm/@docusaurus/plugin-client-redirects@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/@docusaurus/theme-search-algolia@3.9.2 → npm/@docusaurus/core@3.9.2 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report