deps: update axios to 1.8.2 to fix SSRF vulnerability - #3
Merged
Conversation
patrickwang1990
marked this pull request as ready for review
June 8, 2026 16:48
![semgrep-code-octanelending[bot]](https://avatars.githubusercontent.com/u/26302431?s=60&v=4){kind=small}
Regenerated package-lock.json via public npm registry to match CI convention. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
patrickwang1990
force-pushed
the
semgrep-autofix/1779145168
branch
from
June 8, 2026 17:51
f08ac5e to
643ae32
Compare
Semgrep flagged a vulnerability requiring axios >= 1.16.0. Upgrading from 1.8.2 to 1.17.0 (latest) to fully resolve the finding. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Update axios from 1.5.1 to 1.8.2 to address a Server-Side Request Forgery (SSRF) vulnerability.
Changes
Why
Axios versions prior to 1.8.2 do not normalize hostnames before applying
NO_PROXYrules. This allows requests to loopback addresses likelocalhost.or[::1]to be routed through a configured proxy instead of bypassing it. An attacker who can influence request URLs could exploit this to force internal traffic through a malicious proxy, potentially exposing sensitive responses. Version 1.8.2 fixes this hostname normalization issue.Semgrep Finding Details
Affected versions of axios are vulnerable to Server-Side Request Forgery (SSRF) / Unintended Proxy or Intermediary ('Confused Deputy'). Axios does not normalize hostnames before applying
NO_PROXY, so requests to loopback or internal hosts such aslocalhost.or[::1]can be sent through a configured proxy instead of bypassing it. If an attacker can influence request URLs, they may force local/internal Axios traffic through an attacker-controlled proxy, undermining SSRF protections and exposing sensitive responses.Semgrep generated this Autofix PR for this finding from the detection rule ssc-5ea2c631-7cef-a4e0-e641-d179af079827.