Skip to content

[Snyk] Upgrade dompurify from 2.5.6 to 2.5.9#32

Open
cld-sec wants to merge 1 commit intomainfrom
snyk-upgrade-dc102f8fb93d7be53688b03147f49c5e
Open

[Snyk] Upgrade dompurify from 2.5.6 to 2.5.9#32
cld-sec wants to merge 1 commit intomainfrom
snyk-upgrade-dc102f8fb93d7be53688b03147f49c5e

Conversation

@cld-sec
Copy link
Copy Markdown

@cld-sec cld-sec commented Mar 28, 2026

snyk-top-banner

Snyk has created this PR to upgrade dompurify from 2.5.6 to 2.5.9.

ℹ️ 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 3 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-15371376
98 No Known Exploit
Release notes
Package name: dompurify
  • 2.5.9 - 2026-03-05
    • Fixed a possible bypass caused by jsdom's faulty raw-text tag parsing
  • 2.5.8 - 2024-12-09
  • 2.5.7 - 2024-09-26
  • 2.5.6 - 2024-07-05
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.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

Snyk has created this PR to upgrade dompurify from 2.5.6 to 2.5.9.

See this package in npm:
dompurify

See this project in Snyk:
https://app.snyk.io/org/cloudinaryltd/project/83aa05cc-af87-425d-82bc-0a4c312ed022?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants