Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.8amended

Axios: no_proxy bypass via IP alias allows SSRF

CVE-2026-42038GHSA-m7pr-hjqh-92cm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (axios 1.15.1, 0.31.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm axios

    Affected
    >= 1.0.0, < 1.15.1<= 0.31.0
    Fixed in
    0.31.1, 1.15.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-42038: 0.32% estimated exploitation activity in the next 30 days; percentile 25.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The fix for noproxy hostname normalization bypass (#10661) is incomplete.When noproxy=localhost is set, requests to 127.0.0.1 and [::1] still route through the proxy instead of bypassing it. The shouldBypassProxy() function does pure string matching — it does not resolve IP aliases or loopback equivalents. As a result: - noproxy=localhost does NOT block 127.0.0.1 or [::1] - noproxy=127.0.0.1 does NOT block localhost or [::1] POC : process.env.noproxy = 'localhost'; process.env.httpproxy = 'http://attacker-proxy:8888'; <img width="1212" height="247" alt="image" src="https://github.com/user-attachments/assets/0b07ddc4-507d-4b11-a630-15b94ad2c7e7" / Impact: In server-side environments where noproxy is used to prevent requests to internal/cloud metadata services (e.g., 169.254.169.254), an attacker who can influence the URL can bypass the restriction by using an IP alias instead of the hostname, routing the request through an attacker-controlled proxy and leaking internal data. Fix:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-m7pr-hjqh-92cm

  2. Revision 1 · created ·

    Published from osv record GHSA-m7pr-hjqh-92cm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42038

Advisory: Axios: no_proxy bypass via IP alias allows SSRF
IDs: CVE-2026-42038, GHSA-m7pr-hjqh-92cm
Record: https://patchnext.com/advisories/cve-2026-42038 (revision 2, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: axios 1.15.1, 0.31.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm axios: affected >= 1.0.0, < 1.15.1; <= 0.31.0; fixed in 0.31.1, 1.15.1

## Suggested inspection (read-only)
- `npm ls axios --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on axios.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m7pr-hjqh-92cm (OSV record GHSA-m7pr-hjqh-92cm lists affected ranges: npm axios >=1.0.0 =0 <0.31.1 (fixed))
- Verified: https://github.com/advisories/GHSA-m7pr-hjqh-92cm (GitHub-reviewed advisory GHSA-m7pr-hjqh-92cm lists affected ranges: npm axios >=1.0.0 =0 <=0.31.0)

Commands are suggestions: review each one before running it.

Loading voting…