formidable (npm) has 1 known vulnerability, the worst rated LOW. Upgrade to 2.1.3 or later to clear it. No malicious-package signal is recorded.
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 39th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-75v8-2h7p-7m2m, the advisory selected below
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…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for formidable (npm), the worst rated LOW, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for formidable (npm), the worst rated LOW. They are GHSA-75v8-2h7p-7m2m.
2.1.3 or later clears every advisory recorded for formidable (npm). Check the release you pick before installing it.
Search formidable in CyberXYZ Check at https://cyberxyz.io/check?q=formidable. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:04 UTC. The most recent advisory here was published 2025-04-26. Updated continuously from NVD, GHSA, OSV and CNA feeds.