VulnerabilityPublished 24 Apr 2026Updated 27 Apr 2026

CVE-2026-42038: axios · Server-Side Request Forgery

Affects axiosSource GCVE Database

Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.15.1 or 0.31.1 when convenient.

Data as of 12 Nov 2026, 01:03 UTC

CVSS 3.1 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	6.8

Patch: Available – fixed in 1.15.1, 0.31.1

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade axios to 1.15.1 or 0.31.1.

Affected software

Product	Affected	Fixed in
axios axios	Affected >=1.0.0 <1.15.1 <0.31.1	Fixed in 1.15.1 0.31.1

AI-suggested

Upgrade Axios to version 1.15.1 or later, or 0.31.1 or later, where the SSRF vulnerability is fixed. No other mitigation is required as the vendor has provided an official fix.

Description

Axios versions prior to 1.15.1 and 0.31.1 contain a server-side request forgery (SSRF) vulnerability due to incomplete hostname normalization in the no_proxy setting. Specifically, when no_proxy=localhost is configured, requests to loopback IP addresses like 127.0.0.1 and [::1] do not bypass the proxy as intended, because the shouldBypassProxy() function performs only string matching without resolving IP aliases or loopback equivalents. This flaw allows potential SSRF attacks. The vulnerability is fixed in versions 1.15.1 and 0.31.1.

Impact

An attacker can exploit this SSRF vulnerability to make unauthorized requests to internal services by bypassing the intended proxy bypass rules. This can lead to exposure of sensitive internal resources or services accessible only via localhost or loopback addresses. The CVSS score of 6.8 (medium severity) reflects a network attack vector with high confidentiality impact but requires high attack complexity and no privileges.

Summary

Axios, a promise-based HTTP client for browsers and Node.js, had an SSRF vulnerability (CWE-918) in versions prior to 1.15.1 and 0.31.1. The issue stems from incomplete hostname normalization in the no_proxy environment variable handling. When no_proxy=localhost is set, requests to equivalent loopback IP addresses (127.0.0.1 and [::1]) incorrectly route through the proxy instead of bypassing it. The shouldBypassProxy() function uses pure string matching without resolving IP aliases or loopback equivalents, enabling SSRF exploitation. This vulnerability is addressed in Axios versions 1.15.1 and 0.31.1.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/axios/axios/security/advisories/GHSA-m7pr-hjqh-92cm (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 01:03 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats