{"answers":{"affected":"4 open source packages ship an affected version, including formidable. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46653 exists.","fix":"Upgrade formidable to a fixed version for your release line: 2.1.3 or 3.5.3.","what":"CVE-2025-46653 is a low-severity vulnerability in node-formidable Formidable, published on 26 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46653 and fix it if it is affected.\n\nWhat it is: CVE-2025-46653 is a low-severity vulnerability in node-formidable Formidable, published on 26 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46653 exists.\n\nAffected packages and fixed versions:\n- formidable (npm): affected from 2.1.0; fixed in 2.1.3\n- formidable (npm): affected from 2.1.0; fixed in 2.1.3\n- formidable (npm): affected from 3.1.1-canary.20211030; fixed in 3.5.3\n- formidable (npm): affected from 3.1.1-canary.20211030; fixed in 3.5.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46653/ (Markdown: https://insights.sbomify.com/CVE-2025-46653/index.md)","id":"CVE-2025-46653","markdown":"https://insights.sbomify.com/CVE-2025-46653/index.md","name":"CVE-2025-46653","record":{"aliases":["DEBIAN-CVE-2025-46653","GHSA-75v8-2h7p-7m2m","MINI-42fr-3gr3-37v5","ROOT-APP-NPM-CVE-2025-46653","UBUNTU-CVE-2025-46653"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js file upload library","requires_auth":"low_privilege","summary":"The library uses a non-cryptographically secure random generator for filenames, potentially allowing attackers to guess upload paths and bypass security controls.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"formidable","vendor":"node-formidable"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Formidable relies on hexoid to prevent guessing of filenames for untrusted executable content","id":"CVE-2025-46653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":4,"n_references":3,"next":{"headline":"Cross-site scripting in CodiMD","id":"CVE-2025-46654"},"packages":[{"ecosystem":"npm","fixed":["2.1.3"],"introduced":["2.1.0"],"last_affected":[],"package":"formidable","purl":null,"source":"GHSA-75v8-2h7p-7m2m"},{"ecosystem":"npm","fixed":["2.1.3"],"introduced":["2.1.0"],"last_affected":[],"package":"formidable","purl":"pkg:npm/formidable","source":"GHSA-75v8-2h7p-7m2m"},{"ecosystem":"npm","fixed":["3.5.3"],"introduced":["3.1.1-canary.20211030"],"last_affected":[],"package":"formidable","purl":null,"source":"GHSA-75v8-2h7p-7m2m"},{"ecosystem":"npm","fixed":["3.5.3"],"introduced":["3.1.1-canary.20211030"],"last_affected":[],"package":"formidable","purl":"pkg:npm/formidable","source":"GHSA-75v8-2h7p-7m2m"}],"prev":{"headline":"Security feature bypass in IZArc","id":"CVE-2025-46652"},"products":["Formidable"],"published":"2025-04-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["node-formidable"]},"summary":"The library uses a non-cryptographically secure random generator for filenames, potentially allowing attackers to guess upload paths and bypass security controls.","url":"https://insights.sbomify.com/CVE-2025-46653/"}