EUVD-2026-25588
GHSA-pf86-5x62-jrwf
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Lifecycle Timeline
7Blast Radius
ecosystem impact- 273 npm packages depend on axios (189 direct, 84 indirect)
Ecosystem-wide dependent count for version 1.0.0.
DescriptionCVE.org
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, when Object.prototype has been polluted by any co-dependency with keys that axios reads without a hasOwnProperty guard, an attacker can (a) silently intercept and modify every JSON response before the application sees it, or (b) fully hijack the underlying HTTP transport, gaining access to request credentials, headers, and body. The precondition is prototype pollution from a separate source in the same process. This vulnerability is fixed in 1.15.1 and 0.31.1.
AnalysisAI
Prototype pollution in Axios HTTP client versions before 1.15.1 and 0.31.1 enables silent interception and modification of all JSON responses or complete HTTP transport hijacking when the JavaScript Object.prototype has been polluted by a co-dependency. This vulnerability requires a separate prototype pollution source within the same Node.js process but requires no authentication once that precondition exists. An attacker can then access credentials, headers, and request bodies across the application. EPSS data not available; no public exploit identified at time of analysis.
Technical ContextAI
Axios is a widely-used promise-based HTTP client library for Node.js and browser environments, commonly deployed in modern JavaScript applications for API communication. This vulnerability stems from CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes), specifically the absence of hasOwnProperty guards when Axios reads configuration properties from objects. In JavaScript, prototype pollution occurs when an attacker can inject properties into Object.prototype, causing all objects in the application to inherit malicious properties. Axios reads certain configuration keys without verifying they are own properties rather than inherited ones. When a separate vulnerability or malicious dependency pollutes Object.prototype with keys that Axios consumes (such as transport configuration or response transformation hooks), the attacker gains control over Axios's internal behavior. The CVSS vector indicates network attack vector (AV:N) but high complexity (AC:H), reflecting that the attack requires the precondition of existing prototype pollution from another source in the same JavaScript runtime.
RemediationAI
Upgrade Axios to version 1.15.1 or later for 1.x users, or version 0.31.1 or later for 0.x users, as documented in GitHub security advisory GHSA-pf86-5x62-jrwf at https://github.com/axios/axios/security/advisories/GHSA-pf86-5x62-jrwf. These patched versions implement hasOwnProperty guards to prevent reading polluted prototype properties. If immediate upgrade is not feasible, implement defense-in-depth measures: audit all npm dependencies for known prototype pollution vulnerabilities using tools like npm audit or Snyk, freeze Object.prototype using Object.freeze(Object.prototype) at application startup (note this may break legacy code expecting prototype mutability), and implement runtime monitoring for unexpected properties on Object.prototype. For high-risk applications, consider replacing Axios temporarily with alternative HTTP clients that demonstrate prototype pollution resistance, though this carries significant refactoring cost. All compensating controls are partial mitigations only - upgrading to patched versions is the definitive fix.
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
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
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
Directory traversal vulnerability in lib/app/index.js in Geddy before 13.0.8 for Node.js allows remote attackers to read
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Eval injection vulnerability in index.js in the syntax-error package before 1.1.1 for Node.js 0.10.x, as used in IBM Rat
The HTTP server in Node.js 0.10.x before 0.10.21 and 0.8.x before 0.8.26 allows remote attackers to cause a denial of se
Same technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today