Repository navigation
R11DT-4404 - Bump vulnerable deps in swagger-ui - #220
Merged
Merged
Conversation
OS-thiagosiqueira
marked this pull request as ready for review
October 16, 2026 11:39
OS-luisvendrame
previously approved these changes
Oct 16, 2026
rmb-guerra
reviewed
Oct 16, 2026
rmb-guerra
approved these changes
Oct 16, 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.
Jira Issue
R11DT-4404
The problem
Wiz flags
axios@1.18.1against theb11branch: 12 findings (CVE-2026-101898 to CVE-2026-101909, 7 High and 5 Medium), all with fix version1.20.0. The advisories cover ReDoS in thedata:URL parser and in proxy-bypass host normalization, prototype-pollution gadgets in the HTTP and fetch adapters, header injection, redirect-based SSRF (maxRedirects: 0not enforced by the fetch adapter), andNO_PROXYCIDR entries being ignored.npm auditon the same lockfile reports the same range:Proposed solution
Patch-level bump of a transitive dependency only, same surgical-bump pattern as #209 and #207. No
src/changes and nopackage.jsonchange: the existing override"axios": ">=1.18.0"already admits1.20.0, so only the lockfile moves.package-lock.jsonaxios1.18.1→1.20.0; itsform-datarequirement^4.0.5→^4.0.6(the installedform-datawas already4.0.6, so nothing else moves)axiosis only reached throughstart-server-and-test → wait-on(Cypress tooling) andswagger-client → @swagger-api/apidom-reference; both resolve to the single1.20.0copy.Verification:
npm audit— noaxiosfinding left (95 → 94 vulnerable packages, 168 → 156 advisories).npm ls axios— both paths on1.20.0.npm run build— succeeds.Notes / scope
dist/is not part of this PR, on purpose.axiosis not bundled into anydist/file. A rebuild after the bump differs fromHEADonly in theGIT_COMMITandBUILD_TIMEstamps embedded in the bundles (same file length, 60 characters changed), so there is no code change to ship.npm run lint-errors(144 errors) andnpm run test:unit(34 failed tests in 7 suites) fail in files with OutSystems customizations (info.jsx,parameter-row.jsx,model-example.jsx, markdown rendering, and similar). This PR changes none of them, and none of the failures involve network or HTTP code. I did not compare them against a cleanb11run, and the Cypress suite (the only one that exerciseswait-on/axios) was not run.axiosentry now carries the Azure ArtifactsresolvedURL with asha1integrity, as the other 162 entries from that registry do, instead ofregistry.npmjs.orgwithsha512.b11(brace-expansionx3,dompurifyx2) are not touched here.b11branch, so the 12axiosfindings should clear on the first rescan after this is merged.