CVE-2025-46653

LOWNVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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 behavior to upload and execute their own content.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
30
EG Risk 30/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity31% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

Published

April 26, 2025

Last Modified

May 13, 2026

References (4)

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-formidable1.2.1+20200129git8231ea6-1 ... 3.5.4+~cs11.10.5-1 (12 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-formidable3.2.5+20221017git493ec88+~cs4.0.9-1, 3.5.3+~cs11.10.5-1, 3.5.4+~cs11.10.5-1, 3.5.4+~cs11.10.5-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-formidable3.2.5+20221017git493ec88+~cs4.0.9-1, 3.5.3+~cs11.10.5-1, 3.5.4+~cs11.10.5-1, 3.5.4+~cs11.10.5-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-formidable3.2.5+20221017git493ec88+~cs4.0.9-1, 3.5.3+~cs11.10.5-1
  • every version up to 3.5.4+~cs11.10.5-1: fixed in 3.5.4+~cs11.10.5-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
formidable—
  • 3.1.1-canary.20211030 up to 3.5.3: fixed in 3.5.3
  • 2.1.0 up to 2.1.3: fixed in 2.1.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 212 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:10 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 20:14 UTCOSV refresh
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:24 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-28 13:50 UTCEPSS rescore
  13. 2026-09-27 13:45 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-26 00:25 UTCEPSS rescore
  16. 2026-09-24 14:02 UTCEPSS rescore
  17. 2026-09-24 14:02 UTCEPSS rescore
  18. 2026-09-23 13:47 UTCEPSS rescore
  19. 2026-09-21 21:06 UTCEPSS rescore
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-20 20:15 UTCEPSS rescore
  22. 2026-09-18 19:27 UTCEPSS rescore
  23. 2026-09-18 19:27 UTCEPSS rescore
  24. 2026-09-17 19:29 UTCEPSS rescore
  25. 2026-09-17 01:50 UTCOSV refresh
Show 75 more
  1. 2026-09-16 14:07 UTCEPSS rescore
  2. 2026-09-15 03:09 UTCEPSS rescore
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 09:36 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 21:59 UTCEPSS rescore
  8. 2026-09-07 16:00 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-05 15:28 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:38 UTCEPSS rescore
  16. 2026-08-30 19:16 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-29 02:13 UTCOSV refresh
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:45 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 14:16 UTCEPSS rescore
  24. 2026-08-24 09:22 UTCEPSS rescore
  25. 2026-08-23 00:18 UTCEPSS rescore
  26. 2026-08-21 23:48 UTCEPSS rescore
  27. 2026-08-20 22:54 UTCEPSS rescore
  28. 2026-08-19 17:03 UTCEPSS rescore
  29. 2026-08-18 13:47 UTCEPSS rescore
  30. 2026-08-17 13:46 UTCEPSS rescore
  31. 2026-08-16 14:55 UTCEPSS rescore
  32. 2026-08-16 02:13 UTCEPSS rescore
  33. 2026-08-15 01:29 UTCEPSS rescore
  34. 2026-08-13 21:59 UTCEPSS rescore
  35. 2026-08-12 14:13 UTCOSV refresh
  36. 2026-08-12 13:50 UTCEPSS rescore
  37. 2026-08-11 13:41 UTCEPSS rescore
  38. 2026-08-10 23:59 UTCEPSS rescore
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 16:36 UTCEPSS rescore
  41. 2026-08-06 13:46 UTCEPSS rescore
  42. 2026-08-05 19:16 UTCEPSS rescore
  43. 2026-08-04 15:09 UTCEPSS rescore
  44. 2026-08-04 10:37 UTCEPSS rescore
  45. 2026-08-03 10:35 UTCEPSS rescore
  46. 2026-08-02 02:26 UTCEPSS rescore
  47. 2026-08-01 04:15 UTCEPSS rescore
  48. 2026-07-30 16:27 UTCEPSS rescore
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-28 15:35 UTCEPSS rescore
  52. 2026-07-27 21:24 UTCOSV refresh
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-25 14:17 UTCEPSS rescore
  55. 2026-07-25 14:17 UTCEPSS rescore
  56. 2026-07-24 14:17 UTCEPSS rescore
  57. 2026-07-23 14:18 UTCEPSS rescore
  58. 2026-07-23 02:56 UTCEG score recompute
  59. 2026-07-22 14:07 UTCEPSS rescore
  60. 2026-07-22 14:07 UTCEPSS rescore
  61. 2026-07-21 15:24 UTCEPSS rescore
  62. 2026-07-20 17:07 UTCEPSS rescore
  63. 2026-07-19 14:30 UTCEPSS rescore
  64. 2026-07-19 14:30 UTCEPSS rescore
  65. 2026-07-19 02:28 UTCEPSS rescore
  66. 2026-07-19 02:28 UTCEPSS rescore
  67. 2026-07-18 10:04 UTCEPSS rescore
  68. 2026-07-16 17:02 UTCEPSS rescore
  69. 2026-07-16 17:02 UTCEPSS rescore
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 01:59 UTCEPSS rescore
  73. 2026-07-15 01:59 UTCEPSS rescore
  74. 2026-07-13 22:29 UTCEPSS rescore
  75. 2026-07-13 22:29 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:11:node-formidable

Frequently asked(5)

What is CVE-2025-46653?
CVE-2025-46653 is a low vulnerability published on April 26, 2025. 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…
When was CVE-2025-46653 disclosed?
CVE-2025-46653 was first published on April 26, 2025, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-46653 actively exploited?
CVE-2025-46653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-46653?
CVE-2025-46653 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2025-46653?
A fix for CVE-2025-46653 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-46653

Explore →

Is Your Infrastructure Affected by CVE-2025-46653?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs