R11DT-3980 - Bump transitive deps axios and brace-expansion (security) - #204
Merged
OS-alexandretome merged 1 commit intoJun 3, 2026
Conversation
Force patched versions via scoped npm overrides: - axios >=1.16.0 (GHSA-35jp-ww65-95wh, High - prototype pollution -> proxy MITM) - @swagger-api/apidom-reference > brace-expansion >=5.0.6 (GHSA-jxxr-4gwj-5jf2, Medium - ReDoS/memory) Rebuilt dist bundles.
There was a problem hiding this comment.
Pull request overview
This PR addresses two reported transitive dependency vulnerabilities by using npm overrides to force patched versions of axios and brace-expansion, and then rebuilding the distributable dist/ assets so the shipped bundle reflects the updated dependency tree.
Changes:
- Added npm
overridesto enforceaxios >=1.16.0and@swagger-api/apidom-reference→brace-expansion >=5.0.6. - Updated
package-lock.jsonto resolveaxios@1.17.0andbrace-expansion@5.0.6(plus related dependency graph changes). - Rebuilt
dist/assets (CSS and HTML cache-busting hashes updated).
Reviewed changes
Copilot reviewed 1 out of 12 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Adds overrides entries to floor patched transitive versions. |
| package-lock.json | Updates resolved versions for axios and brace-expansion and related lock metadata. |
| dist/swagger-ui.css | Rebuilt CSS bundle output. |
| dist/index.html | Updates cache-busting query hashes for rebuilt assets. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
OS-alexandretome
marked this pull request as ready for review
June 3, 2026 13:23
OS-alexandretome
requested review from
OS-joaomurgeiro,
OS-josecunha,
OS-luisvendrame,
OS-miguelfreitas,
mvios,
osjlopes and
rmb-guerra
and removed request for
a team
June 3, 2026 13:23
Author
osjlopes
approved these changes
Jun 3, 2026
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
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
Patches two transitive vulnerabilities surfaced in the swagger-ui dependency tree:
axiosbrace-expansion(under@swagger-api/apidom-reference)Both are pulled in transitively via
swagger-client→@swagger-api/apidom-reference.dist/bundles rebuilt.Why this approach (scoped
overrides)overridesfloor is enough — no need to touchswagger-client/apidom.<1.16.0), and its brace-expansion fix is adeps-devchange that does not reliably reach the shipped runtime tree. Higher churn, covers neither vuln fully.brace-expansionis scoped under@swagger-api/apidom-referencerather than top-level, to avoid forcing the unrelated 1.x/2.x copies (minimatch, rimraf) into a major-version jump.Risk
Low. swagger-ui is consumed by Platform purely as a browser bundle (REST API doc viewer, "Try It Out" disabled). The axios proxy-MITM vector is Node-only; brace-expansion is at most a self-DoS on a developer-authored spec. Patching primarily clears the security-scanner flag.