GHSA-rm8p-cx58-hcvx json
Transitive Critical Vulnerability via form-data@4.0.0 in axios@1.10.0 — Predictable Boundary Values (CVE-2025-7783)
published last yr. modified 2mo ago also CVE-2025-54371
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository axios/axios. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.5
- version 3.1, the maintainers
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of axios/axios for axios: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- npm axios 1.11.0
Is GHSA-rm8p-cx58-hcvx in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| the maintainers | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | axios | 1.10.0 |
1.11.0 |
References
Sources
- GitHub Advisory GHSA-rm8p-cx58-hcvx
- Maintainer advisory GHSA-rm8p-cx58-hcvx
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of axios/axios published their own advisory on GitHub. Reviewed sources take precedence over it.