Skip to content

[Snyk] Security upgrade dompurify from 3.3.0 to 3.4.0#241

Open
graymalkin77 wants to merge 1 commit intomainfrom
snyk-fix-b24262fa8cef54e58ef8d8c47b6c4801
Open

[Snyk] Security upgrade dompurify from 3.3.0 to 3.4.0#241
graymalkin77 wants to merge 1 commit intomainfrom
snyk-fix-b24262fa8cef54e58ef8d8c47b6c4801

Conversation

@graymalkin77
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Operator Precedence Logic Error
SNYK-JS-DOMPURIFY-16078387
  601  

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@graymalkin77
Copy link
Copy Markdown
Author

Merge Risk: Medium

This is a minor version upgrade for dompurify from 3.3.0 to 3.4.0. The release consists primarily of security fixes and bug fixes related to sanitization logic.

Key Changes:

  • Behavioral Fixes: The update addresses several edge cases where configuration options could be bypassed or lead to unexpected behavior. For example, a fix ensures FORBID_TAGS now correctly overrides ADD_TAGS.
  • Security Patches: The release includes fixes for several potential mutation XSS (mXSS) vulnerabilities and prototype pollution issues.

While this release does not introduce explicitly breaking API changes, the fixes alter sanitization behavior to be more strict and correct. This could potentially affect applications that were unintentionally relying on the previous, less strict behavior.

Recommendation: This upgrade is recommended for its security enhancements. However, due to the behavioral changes in sanitization, it is important to verify that the stricter parsing does not negatively impact legitimate use cases in your application.

Source: GitHub Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Copilot AI review requested due to automatic review settings April 16, 2026 21:38
@graymalkin77
Copy link
Copy Markdown
Author

graymalkin77 commented Apr 16, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Upgrades dompurify to a non-vulnerable version to address Snyk-reported issue SNYK-JS-DOMPURIFY-16078387 (operator precedence logic error).

Changes:

  • Bump dompurify dependency range in package.json to ^3.4.0.
  • Update package-lock.json to lock dompurify to 3.4.0 with updated resolved tarball and integrity hash.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
package.json Updates dompurify dependency version to ^3.4.0.
package-lock.json Locks dompurify to 3.4.0 and updates associated metadata.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

3 participants