CVE-2025-46653: Formidable relies on hexoid to prevent guessing of filenames for untrusted executable content
(updated )
Formidable (aka node-formidable) 2.x before 2.1.3 and 3.x before 3.5.3 relies on hexoid to prevent guessing of filenames for untrusted executable content; however, hexoid is documented as not “cryptographically secure.” (Also, there is a scenario in which only the last two characters of a hexoid string need to be guessed, but this is not often relevant.) NOTE: this does not imply that, in a typical use case, attackers will be able to exploit any hexoid behavior to upload and execute their own content.
References
- github.com/advisories/GHSA-75v8-2h7p-7m2m
- github.com/node-formidable/formidable
- github.com/node-formidable/formidable/blob/d0fbec13edc8add54a1afb9ce1a8d3db803f8d47/CHANGELOG.md?plain=1
- github.com/node-formidable/formidable/commit/022c2c5577dfe14d2947f10909d81b03b6070bf5
- github.com/node-formidable/formidable/commit/37a3e89fca1ed68ec674a539f13aafd62221ddaa
- github.com/zast-ai/vulnerability-reports/blob/main/formidable/file_upload/report.md
- nvd.nist.gov/vuln/detail/CVE-2025-46653
- www.npmjs.com/package/formidable/v/2.1.3
- www.npmjs.com/package/formidable/v/3.5.3
Code Behaviors & Features
Detect and mitigate CVE-2025-46653 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →