axios
npm
SEMVER · introduced 1.10.0 → fixed 1.11.0
1 versions listed as affected
1.10.0
No access to your tenant or devices. Every item links to its source. What this means
This CVE is a duplicate of another CVE.
Read the publisher's advisoryWithdrawn Advisory: Axios has Transitive Critical Vulnerability via form-data
Read the publisher's advisoryRejected reason: This CVE is a duplicate of another CVE.
Read the publisher's advisory### Withdrawn Advisory This advisory has been withdrawn because users of Axios 1.10.0 have the flexibility to use a patched version of form-data, the software in which the vulnerability originates, without upgrading Axios to address GHSA-fjxv-7rqg-78g4. ### Original Description A critical vulnerability exists in the form-data package used by `[email protected]`. The issue allows an attacker to predict multipart boundary values generated using `Math.random()`, opening the door to HTTP parameter pollution or injection attacks. This was submitted in [issue #6969](https://github.com/axios/axios/issues/6969) and addressed in [pull request #6970](https://github.com/axios/axios/pull/6970). ### Details The vulnerable package `[email protected]` is used by `[email protected]` as a transitive dependency. It uses non-secure, deterministic randomness (`Math.random()`) to generate multipart boundary strings. This flaw is tracked under [Snyk Advisory SNYK-JS-FORMDATA-10841150](https://security.snyk.io/vuln/SNYK-JS-FORMDATA-10841150) and [CVE-2025-7783](https://security.snyk.io/vuln/SNYK-JS-FORMDATA-10841150). Affected `form-data` versions: - <2.5.4 - >=3.0.0 <3.0.4 - >=4.0.0 <4.0.4 Since `[email protected]` pulls in `[email protected]`, it is exposed to this issue. ### PoC 1. Install Axios: - `npm install [email protected]` 2.Run `snyk test`: ``` Tested 104 dependencies for known issues, found 1 issue, 1 vulnerable path. ✗ Predictable Value Range from Previous Values [Critical Severity] in [email protected] via [email protected] > [email protected] ``` 3. Trigger a multipart/form-data request. Observe the boundary header uses predictable random values, which could be exploited in a targeted environment. ### Impact - **Vulnerability Type**: Predictable Value / HTTP Parameter Pollution - **Risk**: Critical (CVSS 9.4) - **Impacted Users**: Any application using [email protected] to submit multipart form-data This could potentially allow attackers to: - Interfere with multipart request parsing - Inject unintended parameters - Exploit backend deserialization logic depending on content boundaries ### Related Links [GitHub Issue #6969](https://github.com/axios/axios/issues/6969) [Pull Request #xxxx](https://github.com/axios/axios/pull/xxxx) (replace with actual link) [Snyk Advisory](https://security.snyk.io/vuln/SNYK-JS-FORMDATA-10841150) [form-data on npm](https://www.npmjs.com/package/form-data)
Read the publisher's advisoryNo normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
datePublished: Jul 23, 2025, 4:49:38 PM
dateUpdated: Jul 24, 2025, 1:35:30 PM
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Rejected
published: 2025-07-23T21:15:26.970
lastModified: 2025-07-23T21:15:26.970
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
npm
SEMVER · introduced 1.10.0 → fixed 1.11.0
1.10.0
Original source record · Cite this exact observation · Complete original publisher JSON