CVE-2026-42264: Axios: Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking
Axios is a promise based HTTP client for the browser and Node.js. From version 1.0.0 to before version 1.15.2, fFive config properties (auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser) in the HTTP adapter are read via direct property access without hasOwnProperty guards, making them exploitable as prototype pollution gadgets. When Object.prototype is polluted by another dependency in the same process, axios silently picks up these polluted values on every outbound HTTP request. This issue has been patched in version 1.15.2.
Security readout for executives and security teams
Plain-English summary
Axios could unknowingly use malicious configuration values if another bug has polluted Object.prototype in the same process. In affected versions, this can let outbound HTTP requests receive injected credentials or be redirected through attacker-controlled behavior. The confirmed fix is axios 1.15.2.
Executive priority
Treat as high priority for internet-facing services, API gateways, automation workers, and systems handling secrets in outbound requests. The prerequisite reduces likelihood, but successful abuse could redirect traffic or leak credentials.
Technical view
Axios 1.0.0 through versions before 1.15.2 read auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser via direct property access in the HTTP adapter. Without own-property checks, these fields become prototype pollution gadgets when Object.prototype is already polluted. CVSS is 7.4 high with high attack complexity.
Likely exposure
Most relevant to Node.js or server-side applications using axios's HTTP adapter for outbound requests. Exposure requires vulnerable axios and a separate prototype pollution path in the same process, so inventory alone is necessary but not sufficient to prove exploitability.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Practical abuse requires a prior or concurrent prototype pollution condition, but impact can include credential injection and request hijacking once that condition exists.
Researcher notes
Focus review on request construction paths and polluted inherited values for the five named adapter properties. The root risk is gadget behavior after prototype pollution, not axios alone creating the pollution source. Avoid assuming exploitability without a pollution primitive.
Mitigation direction
Upgrade axios to version 1.15.2 or later.
Update direct and transitive axios dependencies in lockfiles and builds.
Check Red Hat errata if consuming axios through Red Hat products.
Review vendor advisories for product-specific remediation guidance.
Address known prototype pollution flaws in the same application process.
Validation and detection
Search SBOMs and lockfiles for axios versions >=1.0.0 and <1.15.2.
Confirm deployed artifacts include axios 1.15.2 or later.
Identify server-side outbound HTTP paths using axios's HTTP adapter.
Assess whether the same process has known prototype pollution exposure.
Track Red Hat and GitHub advisories for updated affected-product details.
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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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
15Source 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.
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.