Skip to content

SWI-3723 [Snyk] Security upgrade dompurify from 3.3.0 to 3.3.2#42

Open
bwappsec wants to merge 1 commit intomainfrom
snyk-fix-7ae4aafd7505df16fdf56a34a8d4b9e9
Open

SWI-3723 [Snyk] Security upgrade dompurify from 3.3.0 to 3.3.2#42
bwappsec wants to merge 1 commit intomainfrom
snyk-fix-7ae4aafd7505df16fdf56a34a8d4b9e9

Conversation

@bwappsec
Copy link

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
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-15371376
  98  

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)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-DOMPURIFY-15371376
@bwappsec bwappsec requested a review from a team as a code owner March 12, 2026 08:34
@bwappsec
Copy link
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.

@bwappsec bwappsec requested a review from a team as a code owner March 12, 2026 08:34
@bwappsec
Copy link
Author

bwappsec commented Mar 12, 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.

@bwappsec bwappsec changed the title [Snyk] Security upgrade dompurify from 3.3.0 to 3.3.2 SWI-3723 [Snyk] Security upgrade dompurify from 3.3.0 to 3.3.2 Mar 12, 2026
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