Skip to content

[Snyk] Upgrade dompurify from 2.3.3 to 2.5.8#35

Open
blmitkc wants to merge 1 commit intodevelopmentfrom
snyk-upgrade-077f5a2024118c89f34cb708ee852631
Open

[Snyk] Upgrade dompurify from 2.3.3 to 2.5.8#35
blmitkc wants to merge 1 commit intodevelopmentfrom
snyk-upgrade-077f5a2024118c89f34cb708ee852631

Conversation

@blmitkc
Copy link
Owner

@blmitkc blmitkc commented Aug 12, 2025

snyk-top-banner

Snyk has created this PR to upgrade dompurify from 2.3.3 to 2.5.8.

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

  • The recommended version was released 8 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Prototype Pollution
SNYK-JS-DOMPURIFY-7984421
586 No Known Exploit
medium severity Template Injection
SNYK-JS-DOMPURIFY-6474511
586 Proof of Concept
medium severity Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-8184974
586 Proof of Concept
critical severity Prototype Pollution
SNYK-JS-DOMPURIFY-8318045
586 No Known Exploit

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.3.3 to 2.5.8.

See this package in yarn:
dompurify

See this project in Snyk:
https://app.snyk.io/org/blmitkc/project/28fbc5e4-5810-41ec-9996-d93d9ba2c939?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