Skip to content

fix: upgrade DOMPurify to 3.4.17 for three new advisories - #69

Merged
ValentinTorassa merged 1 commit into
mainfrom
fix/dompurify-advisory
Oct 23, 2026
Merged

ValentinTorassa merged 1 commit into
mainfrom
fix/dompurify-advisory

Conversation

@ValentinTorassa

Copy link
Copy Markdown
Owner

Hoy se publicaron tres avisos que afectan a dompurify 3.4.16, que entra por Mermaid (^3.4.12): GHSA-cg2g-xh64-v4q7 (crítico), GHSA-mrv2-3pqr-j5jr y GHSA-c6gr-qvv4-5v3f. npm run audit empezó a fallar en main con el merge de #68, aunque ese PR no tiene nada que ver.

El cambio solo toca package-lock.json: dompurify pasa a 3.4.17. Con eso, npm audit no encuentra vulnerabilidades y npm run audit pasa en local.

Mermaid pulls dompurify ^3.4.12. 3.4.16 is affected by GHSA-cg2g-xh64-v4q7 (critical), GHSA-mrv2-3pqr-j5jr and GHSA-c6gr-qvv4-5v3f, which made npm run audit fail on main after #68.
@vercel

vercel Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
open-security-labs Ready Ready Preview Oct 23, 2026 12:12pm UTC

@ValentinTorassa
ValentinTorassa merged commit 1902d34 into main Oct 23, 2026
6 checks passed
@ValentinTorassa
ValentinTorassa deleted the fix/dompurify-advisory branch October 23, 2026 12:17

This branch was successfully deployed

1 active deployment
Preview — 885d9290 Deployed Oct 23, 2026 by vercel[bot]
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.

1 participant