fix: bump axios to ^1.15.0 to patch NO_PROXY SSRF bypass (PMAA-94)#270
Merged
gaurav-singh-9227 merged 2 commits intobrowserstack:mainfrom Apr 13, 2026
Merged
Conversation
) Upgrade axios from 1.14.0 to 1.15.0 to remediate GHSA-3p68-rc4w-qgx5, where NO_PROXY hostname normalization could be bypassed via trailing-dot hostnames or IPv6 literals, leading to SSRF. Ref PMAA-94. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… server.json Version bump for the axios 1.15.0 security upgrade (PMAA-94 / CVE-2025-62718). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
gaurav-singh-9227
approved these changes
Apr 13, 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.
Summary
axiosfrom 1.14.0 → 1.15.0 to remediate GHSA-3p68-rc4w-qgx5 / CVE-2025-62718 — NO_PROXY hostname-normalization bypass leading to SSRF (CVSSv4 9.3, critical).Vulnerability
Axios
<1.15.0did a literal string comparison againstNO_PROXYand did not normalize hostnames. Requests tohttp://localhost.:PORT/(trailing dot) orhttp://[::1]:PORT/(IPv6 literal) skippedNO_PROXYmatching and were routed through the configured proxy — enabling SSRF / proxy-bypass when apps relied onNO_PROXY=localhost,127.0.0.1,::1to protect loopback services.Fixed upstream by axios/axios#10661, released in v1.15.0.
Changes
package.json:axios: "^1.14.0"→"^1.15.0"package-lock.json: regenerated for axios 1.15.0No source changes required — the fix lives inside axios'
NO_PROXYevaluation logic, which oursrc/lib/apiClient.tswrapper consumes transparently.Impact assessment
src/lib/apiClient.tsandsrc/lib/error.ts(+ a test file). The public surface (AxiosRequestConfig,AxiosResponse,axios.create, per-verb methods,httpsAgent) is unchanged.tsc --noEmit) passes clean.npm auditsurfaces 4 other unrelated advisories (vite, hono, @hono/node-server, basic-ftp) — out of scope for this ticket.Verification
Ran a local verification harness (not committed) against the upgraded axios:
axios.get("https://api.github.com/zen")→200 OK✅HTTP_PROXY=http://127.0.0.1:<port>andNO_PROXY=localhost,127.0.0.1,::1, then issued requests tohttp://localhost.:9999/andhttp://[::1]:9999/. The proxy received zero hits, confirming axios 1.15.0 correctly normalizes trailing-dot hostnames and IPv6 literals before matchingNO_PROXY. On axios 1.14.0 both requests would have been routed to the proxy. ✅Test plan
npx tsc --noEmit— no errorsnpm test— 123/123 passing🤖 Generated with Claude Code