Skip to content

[Snyk] Security upgrade dompurify from 3.3.0 to 3.3.2#235

Open
graymalkin77 wants to merge 1 commit intomainfrom
snyk-fix-3581dde5db02a3cd854922ffe1e3c145
Open

[Snyk] Security upgrade dompurify from 3.3.0 to 3.3.2#235
graymalkin77 wants to merge 1 commit intomainfrom
snyk-fix-3581dde5db02a3cd854922ffe1e3c145

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 Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-15371376
  541  

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:

🦉 Cross-site Scripting (XSS)

@graymalkin77
Copy link
Copy Markdown
Author

Merge Risk: Medium

This is a patch upgrade that includes security fixes and bug corrections.

Highlights:

  • v3.3.2: This version addresses a potential bypass in jsdom, a prototype pollution issue, and fixes lenient configuration parsing.
  • v3.3.1: This version extended the ADD_FORBID_CONTENTS setting and corrected the ESM import syntax.

Potential Impact:
The fix for "lenient config parsing in _isValidAttribute" in version 3.3.2 introduces stricter validation. While this is a bug fix, it could be a behavioral change for any implementation that was unintentionally relying on the previous, more lenient parsing. This change warrants a medium risk assessment.

Recommendation:
Verify that any custom configurations for DOMPurify attributes are still behaving as expected after the upgrade.

Source: GitHub Releases

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 March 6, 2026 21:37
@graymalkin77
Copy link
Copy Markdown
Author

graymalkin77 commented Mar 6, 2026

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

Status Scanner 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

This PR updates the dompurify dependency to a patched version to address the Snyk-reported XSS vulnerability in this project’s sanitization stack.

Changes:

  • Bump dompurify dependency range to ^3.3.2 in package.json.
  • Update package-lock.json to install [email protected] (including its Node engine metadata).

Reviewed changes

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

File Description
package.json Updates declared dompurify dependency to ^3.3.2.
package-lock.json Locks dompurify to 3.3.2 and updates resolved/integrity metadata accordingly.

💡 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