CVE-2025-46653: Formidable (aka node-formidable) 2.1.0 through 3.x before 3.5.3 relies on hexoid to prevent guessing of filena

Q: How do I fix CVE-2025-46653?

formidable: upgrade to 3.5.3. Exact commands for each OS are on this page.

Q: Is CVE-2025-46653 being exploited?

CVE-2025-46653 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-46653 affect?

CVE-2025-46653 affects formidable. Severity is low (CVSS 3.1). Formidable (aka node-formidable) 2.1.0 through 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

Q: How urgent is CVE-2025-46653?

Priority 26/100. Public exploit reference

Routine

LOW 3.1UPGRADE

CVE-2025-46653 is a low-severity flaw (CVSS 3.1) affecting formidable. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Formidable (aka node-formidable) 2.1.0 through 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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	3.1 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 61%)
CISA exploited list	No
Weakness	CWE-338
Published	2025-04-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: node-formidable

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-04-26 21:15 UTCPublished CVE record published
2026-06-17 09:26 UTCUpdated Record last modified

node-formidable formidable UPGRADE

Affected: >= 2.1.0 and < 3.5.3

Fixed in: 3.5.3

Safe to downgrade to: a release before 2.1.0

1. Check installed version

npm ls formidable

2. UPGRADE to 3.5.3

npm install formidable@">=3.5.3"

3. If no update is available yet, DOWNGRADE to a release before 2.1.0

npm view formidable versions npm install formidable@"<2.1.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-46653?

formidable: upgrade to 3.5.3. Exact commands for each OS are on this page.

Is CVE-2025-46653 being exploited?

CVE-2025-46653 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-46653 affect?

CVE-2025-46653 affects formidable. Severity is low (CVSS 3.1). Formidable (aka node-formidable) 2.1.0 through 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

How urgent is CVE-2025-46653?

Priority 26/100. Public exploit reference

References

← Back to latest CVEs