Skip to content
This repository was archived by the owner on Jul 14, 2026. It is now read-only.

[Snyk] Security upgrade dompurify from 3.4.2 to 3.4.6 - #13926

Closed
kw-security wants to merge 1 commit into
masterfrom
snyk-fix-4cffc0c76833e46f2a58bac75a67f1c8
Closed

kw-security wants to merge 1 commit into
masterfrom
snyk-fix-4cffc0c76833e46f2a58bac75a67f1c8

Conversation

@kw-security

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

  • packages/web-runtime/package.json
⚠️ Warning
Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Trust Boundary Violation
SNYK-JS-DOMPURIFY-17344526
  108  
medium severity Prototype Pollution
SNYK-JS-DOMPURIFY-17344538
  108  

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:

🦉 Prototype Pollution

@kw-security

Copy link
Copy Markdown
Contributor Author

Merge Risk: Medium

This is a patch-level upgrade that contains several security fixes between versions 3.4.2 and 3.4.6.

Key Changes:

  • Stricter Sanitization: The updates address multiple XSS bypass vulnerabilities. This results in stricter HTML sanitization.
  • Behavioral Change: While not an API breaking change, previously accepted HTML that exploited these vulnerabilities will now be sanitized differently. This could be considered a behavioral change that requires verification.

Recommendation:
This upgrade is recommended for security. However, due to the stricter sanitization rules, it is advisable to test that legitimate HTML content is still handled 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.

@update-docs

update-docs Bot commented Jul 1, 2026

Copy link
Copy Markdown

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@kw-security

kw-security commented Jul 1, 2026 •

Copy link
Copy Markdown
Contributor Author

✅ 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.

@sonarqubecloud

sonarqubecloud Bot commented Jul 1, 2026

Copy link
Copy Markdown

@LukasHirt

Copy link
Copy Markdown
Collaborator

Web repo is going to be archived and will no longer accept new PRs. Please, use owncloud/ocis repository instead.

@LukasHirt LukasHirt closed this Jul 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants