Skip to content

Withdrawn Advisory: Axios has Transitive Critical Vulnerability via form-data

High severity GitHub Reviewed Published Jul 23, 2025 in axios/axios • Updated Jul 24, 2025
Withdrawn This advisory was withdrawn on Jul 24, 2025

Package

npm axios (npm)

Affected versions

= 1.10.0

Patched versions

1.11.0

Description

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 and addressed in pull request #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 and CVE-2025-7783.

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

Pull Request #xxxx (replace with actual link)

Snyk Advisory

form-data on npm

References

@jasonsaayman jasonsaayman published to axios/axios Jul 23, 2025
Published to the GitHub Advisory Database Jul 23, 2025
Reviewed Jul 23, 2025
Published by the National Vulnerability Database Jul 23, 2025
Withdrawn Jul 24, 2025
Last updated Jul 24, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

Weaknesses

No CWEs

CVE ID

CVE-2025-54371

GHSA ID

GHSA-rm8p-cx58-hcvx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.