fix: bump @nestjs/swagger and force swagger-ui-dist >=5.19 to drop vulnerable DOMPurify - #658
Merged
mikhail-egorov merged 1 commit intoSep 1, 2026
Conversation
…lnerable DOMPurify
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio. |
API E2E Test Results185 tests 185 ✅ 10s ⏱️ Results for commit c0a401c. |
API Prividium E2E Test Results9 tests 9 ✅ 3s ⏱️ Results for commit c0a401c. |
Unit Test Results 4 files 281 suites 8m 56s ⏱️ Results for commit c0a401c. |
|
Visit the preview URL for this PR: |
Nexus2k
approved these changes
Sep 1, 2026
jodator
approved these changes
Sep 1, 2026
mikhail-egorov
deleted the
me-priv-224-bump-nestjsswagger-in-block-explorer-to-drop-vulnerable
branch
September 1, 2026 14:13
|
🎉 This PR is included in version 3.29.10 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What ❔
Drops the vulnerable DOMPurify bundled inside the Swagger UI served by the API at
/docs(PRIV-224):packages/api: bump@nestjs/swagger^7.0.0→^8.1.1— the latest line compatible with NestJS 10.package.json: add an npm override forcingswagger-ui-distto^5.32.14(8.1.1 alone would still pin5.18.2, which carries DOMPurify 3.1.6).package-lock.json: the resulting resolution —@nestjs/swagger@8.1.1,swagger-ui-dist@5.32.14,@nestjs/mapped-types@2.0.6, and new transitive@scarf/scarf@1.4.0.The served
swagger-ui-bundle.jsnow embeds DOMPurify 3.4.13 (patched in 3.2.4).Why ❔
DOMPurify < 3.2.4 (CVE-2025-26791) inside the
swagger-ui-bundle.jsserved by/docs. Not exploitable — the CVE requires DOMPurify'sSAFE_FOR_TEMPLATESoption, which Swagger UI never sets, and/docsis auth-gated in Prividium mode.Checklist