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.
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.
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.
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.
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.
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.
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.
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.
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.