LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44492: Axios: shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)

Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios does not normalise IPv4-mapped IPv6 addresses. When NO_PROXY lists an IPv4 address such as 127.0.0.1 or 169.254.169.254, a request URL using the IPv4-mapped IPv6 form (::ffff:7f00:1, ::ffff:a9fe:a9fe) still routes through the configured proxy. Node.js resolves these addresses to the underlying IPv4 host, so the request reaches the internal service via the proxy rather than being blocked. This vulnerability is fixed in 0.32.0 and 1.16.0.

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

Security readout for executives and security teams

Plain-English summary

Axios can ignore a NO_PROXY protection when an internal IPv4 address is written in IPv4-mapped IPv6 form. Services that rely on Axios and proxy rules to avoid internal destinations may still send traffic through a proxy. The main business concern is unintended access to sensitive internal endpoints or metadata services.

Executive priority

Prioritize remediation for internet-facing or multi-tenant services that fetch URLs, call webhooks, process integrations, or run in cloud environments with metadata services.

Technical view

Before Axios 0.32.0 and 1.16.0, shouldBypassProxy does not normalize IPv4-mapped IPv6 addresses. NO_PROXY entries such as 127.0.0.1 or 169.254.169.254 may not match equivalent IPv6-mapped forms, while Node.js resolves them to the IPv4 target. The issue is linked to CWE-289 and CWE-918.

Likely exposure

Exposure is most likely in Node.js applications using affected Axios versions with proxy configuration and NO_PROXY rules for localhost, link-local, metadata, or other internal IP addresses.

Exploitation context

The CVE is not listed as KEV in the supplied data, and the bundle does not cite active exploitation. The vulnerability is remotely reachable in affected request paths where attacker-controlled or influenced URLs are fetched through Axios.

Researcher notes

This is described as an incomplete fix for CVE-2025-62718. Validation should focus on proxy-bypass logic, IPv4-mapped IPv6 normalization, and whether application URL controls prevent requests toward internal services.

Mitigation direction

  • Upgrade Axios to 0.32.0, 1.16.0, or later.
  • Review vendor guidance for downstream Red Hat package fixes.
  • Audit NO_PROXY rules that protect internal or metadata IP addresses.
  • Restrict server-side URL fetch features to approved destinations.
  • Monitor proxy logs for unusual internal-address requests.

Validation and detection

  • Inventory applications and containers for affected Axios versions.
  • Confirm dependency resolution uses Axios 0.32.0, 1.16.0, or later.
  • Identify Node.js services using Axios with proxy environment variables.
  • Review SSRF controls around user-influenced outbound requests.
  • Check Red Hat advisories for affected packaged components.
Prepared
Confidence
high
Sources
8

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-289: 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-44492 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
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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
34Source 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
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94GitHub_M
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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: Proxy bypass via IPv4-mapped IPv6 address non-normalization
other:Red Hat severity ratingcvssV3_1
  • 2026-06-11T17:00:56.761Z: Reported to Red Hat.
  • 2026-06-11T15:29:13.890Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiosaxios>= 1.0.0, < 1.16.0, < 0.32.0Listed
Weakness

CWE details

CWE-289CWE-918

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

CWE-289 · source CWE mapping

Authentication Bypass by Alternate Name

Authentication Bypass by Alternate Name represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs