LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44494: Axios: Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

Axios is a promise based HTTP client for the browser and Node.js. From 1.0.0 to before 1.16.0, the Axios library is vulnerable to a Prototype Pollution "Gadget" attack that allows any Object.prototype pollution in the application's dependency tree to be escalated into a full Man-in-the-Middle (MITM) attack — intercepting, reading, and modifying all HTTP traffic including authentication credentials. The HTTP adapter at lib/adapters/http.js:670 reads config.proxy via standard property access, which traverses the prototype chain. Because proxy is not present in Axios defaults, the merged config object has no own proxy property, making it trivially injectable via prototype pollution. Once injected, setProxy() routes all HTTP requests through the attacker's proxy server. This vulnerability is fixed in 1.16.0.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Axios versions 1.0.0 through before 1.16.0 can let an existing prototype pollution bug redirect Axios HTTP traffic through an attacker-controlled proxy. That could expose or alter credentials and API data. The source bundle identifies a fix in Axios 1.16.0. It does not show confirmed active exploitation or KEV listing.

Executive priority

Treat as high priority where Axios protects or transports sensitive business data. The bug needs another prototype pollution condition, but successful abuse could compromise confidentiality and integrity of HTTP traffic.

Technical view

The issue is a prototype pollution gadget in Axios HTTP adapter handling of config.proxy. Standard property access can traverse Object.prototype because proxy is not an own default property. If another flaw pollutes Object.prototype, Axios may route requests through an injected proxy via setProxy().

Likely exposure

Applications using axios >=1.0.0 and <1.16.0 are in scope. Practical exposure is highest in Node.js services making outbound HTTP requests where another dependency or input path can create Object.prototype pollution.

Exploitation context

The CVSS vector rates attack complexity high and privileges/user interaction not required. Sources describe escalation from any Object.prototype pollution to MITM. No KEV listing or provided source confirms active exploitation in the wild.

Researcher notes

Focus validation on whether vulnerable Axios code is reachable in server-side HTTP adapter paths and whether prototype pollution exists elsewhere. Do not assume exploitability from package presence alone; confirm version, adapter usage, and pollution preconditions.

Mitigation direction

  • Upgrade direct axios dependencies to 1.16.0 or later.
  • Apply relevant Red Hat errata for packaged affected components.
  • Audit dependency trees for prototype pollution vulnerabilities.
  • Check vendor guidance before relying on configuration workarounds.
  • Prioritize services sending credentials or sensitive API traffic.

Validation and detection

  • Inventory axios versions in application and container dependency manifests.
  • Confirm runtime dependency resolution does not keep axios below 1.16.0.
  • Review Node.js services using Axios for outbound authenticated requests.
  • Check scanners and SBOMs for CVE-2026-44494 findings.
  • Verify Red Hat advisory applicability for deployed products.
Prepared
Confidence
high
Sources
7

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-1321: 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 · low confidence lookup

CWE-915: 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
cve · low confidence lookup

CVE-2026-44494 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.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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
38Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

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.7CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N2.25.8GitHub_M
8.7CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N2.25.8redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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: Man-in-the-Middle (MITM) attack via Prototype Pollution
other:Red Hat severity ratingcvssV3_1
  • 2026-06-11T17:01:12.945Z: Reported to Red Hat.
  • 2026-06-11T15:32:03.155Z: Made public.

Source materials

Affected products

Products and packages named in the record

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

CWE details

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

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-441 · source CWE mapping

Unintended Proxy or Intermediary ('Confused Deputy')

Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-915 · source CWE mapping

Improperly Controlled Modification of Dynamically-Determined Object Attributes

Improperly Controlled Modification of Dynamically-Determined Object Attributes represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.