CVE-2025-7783: form-data · Weak Randomness
Affects form-dataSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical : upgrade to 2.5.4 as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.4
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade form-data to 2.5.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmform-datapkg:npm/form-dataOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, organizations should implement strict input validation and sanitization on all HTTP parameters to detect and reject duplicated or suspicious parameter names. Web application firewalls (WAFs) can be configured to detect and block HTTP Parameter Pollution attempts by inspecting incoming requests for anomalous parameter patterns. Developers should review application logic to ensure it does not rely on ambiguous parameter handling and enforce explicit parameter parsing strategies. Security teams should conduct thorough code audits and penetration testing focused on parameter handling vulnerabilities. Monitoring and logging of HTTP requests should be enhanced to detect potential exploitation attempts. Additionally, organizations should educate developers and operations teams about the risks of insufficient randomness in security-critical components and promote secure coding practices. Finally, maintaining an inventory of software dependencies and their versions will facilitate rapid response to such vulnerabilities.
Description
Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js. This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.