LiveActive security incident?Get immediate response
CVE Record

CVE-2026-42043: Axios: Incomplete Fix for CVE-2025-62718 — NO_PROXY Protection Bypassed via RFC 1122 Loopback Subnet (127.0.0.0/8) in Axios 1.15.0

Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, an attacker who can influence the target URL of an Axios request can use any address in the 127.0.0.0/8 range (other than 127.0.0.1) to completely bypass the NO_PROXY protection. This vulnerability is due to an incomplete for CVE-2025-62718, This vulnerability is fixed in 1.15.1 and 0.31.1.

HighCVSS 7.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Axios versions before 1.15.1 and 0.31.1 can mishandle proxy bypass rules. If an application lets users influence outbound request URLs, an attacker may route requests around NO_PROXY protections using loopback-range addresses. This can expose internal-only services to limited confidentiality or integrity impact.

Executive priority

Prioritize for internet-facing services that fetch user-supplied URLs or integrate with webhooks, previews, imports, or URL validation flows. Treat as a high-priority dependency update where Axios is used server-side with proxy controls.

Technical view

This is an incomplete fix for CVE-2025-62718. Axios fails to treat the broader RFC 1122 127.0.0.0/8 loopback subnet consistently for NO_PROXY protection. The advisory maps this to CWE-918 SSRF-related behavior and related filter-bypass weaknesses. CVSS is 7.2, high.

Likely exposure

Most relevant to Node.js applications using Axios server-side, proxy configuration, and user-controlled or externally influenced destination URLs. Browser-only Axios usage is less likely to match the described exposure. Inventory direct and transitive Axios dependencies.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires influence over the target URL of an Axios request and an environment where NO_PROXY is relied on to protect loopback or internal access.

Researcher notes

Key issue is trust-boundary bypass around loopback subnet matching, not general Axios request execution. Validate exposure by dependency version, server-side usage, proxy configuration, and user-controlled destinations. Evidence is limited to advisories and Red Hat tracking in the provided bundle.

Mitigation direction

  • Upgrade Axios to 1.15.1, 0.31.1, or later supported fixed versions.
  • Review Red Hat advisories if Axios is consumed through Red Hat-distributed components.
  • Restrict user influence over outbound request destinations where possible.
  • Check vendor guidance for any product-specific backports or packaging status.

Validation and detection

  • Search dependency manifests and lockfiles for Axios versions before 1.15.1 or 0.31.1.
  • Identify services using Axios with proxy or NO_PROXY settings.
  • Review code paths where external input influences Axios request URLs.
  • Confirm patched package versions in deployed build artifacts and containers.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-183: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-441: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-42043 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
42Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7GitHub_M
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-42043Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPaxios: Axios: NO_PROXY bypass via crafted URL
other:Red Hat severity ratingcvssV3_1
  • 2026-04-24T19:01:22.552Z: Reported to Red Hat.
  • 2026-04-24T17:54:42.668Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiosaxios>= 1.0.0, < 1.15.1, < 0.31.1Listed
Weakness

CWE details

CWE-183CWE-441CWE-918

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.