Skip to content

fix(security): bump dompurify to 3.4.17 - #680

Open
hitesh-shetty-cstk wants to merge 1 commit into
mainfrom
fix/dompurify-upgrade
Open

fix(security): bump dompurify to 3.4.17#680
hitesh-shetty-cstk wants to merge 1 commit into
mainfrom
fix/dompurify-upgrade

Conversation

@hitesh-shetty-cstk

@hitesh-shetty-cstk hitesh-shetty-cstk commented Nov 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

DOMPurify had multiple disclosed sanitizer-bypass XSS vulnerabilities in versions up to 3.4.16, all fixed in 3.4.17. This bumps the pinned dompurify dependency range from ^3.4.16 to ^3.4.17 in package.json and updates package-lock.json accordingly.

This is a patch-level bump with no breaking API changes; the single DOMPurify.sanitize(...) call site in the codebase is unaffected.

Generated by Claude Code

@claude
fix(security): bump dompurify to patch XSS vulnerabilities
c6e2313 
DOMPurify versions up to 3.4.16 had multiple disclosed sanitizer-bypass
XSS vulnerabilities, all fixed in 3.4.17. Bump the pinned dependency
range from ^3.4.16 to ^3.4.17 and update the lockfile accordingly.

The sanitize() API used in src/visualBuilder/utils/collabUtils.ts is
unchanged by this patch release.

Co-Authored-By: Claude <noreply@anthropic.com>
@hitesh-shetty-cstk
hitesh-shetty-cstk requested a review from a team as a code owner November 4, 2026 11:39
@snyk-io

snyk-io Bot commented Nov 4, 2026 •
edited
Loading

Copy link
Copy Markdown

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

@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 68.72% 2597 / 3779
🔵 Statements 67.6% 2640 / 3905
🔵 Functions 66.28% 468 / 706
🔵 Branches 63.07% 1573 / 2494
File CoverageNo changed files found.
Generated in workflow #967 for commit c6e2313 by the Vitest Coverage Report Action

@hitesh-shetty-cstk Claude

hitesh-shetty-cstk commented Nov 4, 2026

Copy link
Copy Markdown
Contributor Author

The test check failed once on src/visualBuilder/__test__/click/fields/tags.test.tsx > restricted tags field disables the edit button (100s timeout) — unrelated to this PR's dompurify bump (nothing in that test touches HTML sanitization). Re-ran the failed job and it passed cleanly, confirming it was a flake/slow-runner timeout rather than something this change introduced. All checks are now green.

🤖 Generated with Claude Code

Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@hitesh-shetty-cstk @claude