EUVD-2026-51847
GHSA-68jp-44vc-2x5h
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
AC:H reflects mandatory chaining with a prior prototype pollution primitive and a specific interceptor pattern; no availability impact and limited integrity from proxy-injected responses.
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
3Blast Radius
ecosystem impact- 547 npm packages depend on axios (26 direct, 523 indirect)
Ecosystem-wide dependent count for version 0.31.1.
DescriptionCVE.org
axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled proxy. axios hardens merged request configuration by creating a null-prototype object, but request interceptors run after the merge; a common immutable interceptor pattern such as {...config} or Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an attacker-controlled proxy. For plaintext HTTP requests, the proxy can observe Authorization headers, Basic auth from config.auth, method, absolute URL, Host, and request body, and can return its own response. This does not establish browser impact or HTTPS header/body disclosure under normal TLS validation. Affected versions are >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0).
AnalysisAI
Prototype pollution via the Node.js HTTP adapter in axios allows an attacker who controls Object.prototype.proxy to silently reroute plaintext HTTP requests through an attacker-controlled proxy, exposing Authorization headers, Basic auth credentials, request method, absolute URL, Host, and body content. Affected are axios versions >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0) running in Node.js environments. No public exploit or CISA KEV listing has been identified, but the CVSS 4.0 score of 8.3 with AT:P reflects that exploitation requires a prior or concurrent prototype pollution primitive elsewhere in the same process.
Technical ContextAI
axios (CPE: cpe:2.3:a:axios:axios) is a promise-based HTTP client for Node.js and browsers, distributed via npm. The root cause (CWE-200, Exposure of Sensitive Information) lies in a gap between axios's config-hardening step and its interceptor pipeline. lib/core/mergeConfig.js creates a null-prototype merged config object, which intentionally blocks reads from the prototype chain. However, lib/core/Axios.js runs request interceptors after this merge; any interceptor using the common immutable pattern {...config} or Object.assign({}, config) produces a regular object, re-enabling prototype chain reads. The Node.js HTTP adapter subsequently reads config.proxy through that chain. If an attacker has already polluted Object.prototype.proxy - a primitive available from any number of unrelated JSON-parsing or object-merging flaws - axios will use the attacker-specified proxy for HTTP requests. The Node fetch adapter and all browser adapters are not affected because they resolve proxy settings through different code paths.
RemediationAI
The primary fix is to upgrade axios to version 0.33.0 (for the 0.x branch) or 1.18.0 (for the 1.x branch), both confirmed as fixed releases per GHSA-gcfj-64vw-6mp9 and EUVD-2026-51847. Patch commits and PRs are available at https://github.com/axios/axios/commit/df53d7dd99b202fb194217abd127ae6a630e70dc and https://github.com/axios/axios/pull/11000 and https://github.com/axios/axios/pull/11001. For teams that cannot immediately upgrade, actionable compensating controls include: auditing and remediating any prototype-pollution vulnerabilities in the same Node.js process (remove the prerequisite entirely); rewriting request interceptors to return the original config object rather than a spread or Object.assign clone (this eliminates the hardening bypass path); setting an explicit own proxy: false in the default axios config to override any inherited prototype value (low trade-off, prevents unintended proxy routing); and migrating affected calls to the Node fetch adapter, which is not vulnerable. Each of these workarounds addresses a different link in the exploit chain and can be layered for defense in depth while a patch window is arranged.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Linux Enterprise Module for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| openSUSE Leap 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP3 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP4 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP5 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP3 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP4 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today