LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44486: Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection

Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios’ Node.js HTTP adapter can leak proxy credentials to a redirect target in affected versions. When a request is sent through an authenticated proxy, Axios may add a Proxy-Authorization header. If Axios then follows a redirect and the redirected request is no longer sent through that proxy, the stale Proxy-Authorization header can remain on the redirected request and be sent to the redirect target. This affects Node.js's use of Axios with automatic redirects enabled and an authenticated proxy configuration. Browser adapters are not affected. This vulnerability is fixed in 0.32.0 and 1.16.0.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-44486 can expose proxy credentials from Node.js applications using Axios. If Axios follows a redirect after using an authenticated proxy, it may send the old Proxy-Authorization header to the redirected site. The main business risk is credential disclosure, not system takeover.

Executive priority

Treat as a high-priority credential exposure issue for server-side applications. Prioritize internet-facing or partner-integrating services that make outbound Axios requests through authenticated proxies.

Technical view

Affected Axios versions before 0.32.0 and 1.16.0 can retain a Proxy-Authorization header across redirects when the redirected request is no longer sent through the proxy. Scope is Axios Node.js HTTP adapter with authenticated proxy configuration and automatic redirects. Browser adapters are not affected.

Likely exposure

Exposure is most likely in server-side Node.js services using affected Axios versions with authenticated proxies and redirect following enabled. Browser-only Axios use is not affected according to the source bundle.

Exploitation context

The source bundle marks KEV as false and does not cite active exploitation. The vulnerability is remotely reachable in vulnerable request flows, but exploitation depends on a redirect path receiving the stale proxy credential header.

Researcher notes

Evidence is specific to Axios Node.js HTTP adapter behavior. The sources name fixed versions and affected ranges, but do not provide active exploitation evidence, exploit code status, or a complete downstream product inventory.

Mitigation direction

  • Upgrade Axios to 0.32.0 or 1.16.0 or later.
  • Inventory Node.js dependency trees for affected Axios ranges.
  • Prioritize services using authenticated proxies and automatic redirects.
  • Check Red Hat advisories for packaged or bundled Axios exposure.
  • Rotate proxy credentials if disclosure is suspected.

Validation and detection

  • Confirm deployed Axios versions are not in affected ranges.
  • Identify Node.js services using Axios with authenticated proxy configuration.
  • Verify redirect-following behavior in relevant outbound request paths.
  • Confirm browser-only Axios usage is excluded from impact.
  • Review logs for unexpected Proxy-Authorization disclosure indicators.
Prepared
Confidence
high
Sources
6

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 · medium confidence lookup

CWE-200: 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
cwe · medium confidence lookup

CWE-201: 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-44486 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
30Source 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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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: Information disclosure of proxy credentials via HTTP redirects
other:Red Hat severity ratingcvssV3_1
  • 2026-06-11T17:01:30.944Z: Reported to Red Hat.
  • 2026-06-11T15:39:07.714Z: 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-200CWE-201

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

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

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs