{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62001 exists.","fix":"No fix has been published for CVE-2025-62001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62001 is a high-severity vulnerability in BullWall Ransomware Containment, published on 18 Dec 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-62001 and fix it if it is affected.\n\nWhat it is: CVE-2025-62001 is a high-severity vulnerability in BullWall Ransomware Containment, published on 18 Dec 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-62001 exists.\n\nAffected product: BullWall Ransomware Containment. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-62001/ (Markdown: https://insights.sbomify.com/CVE-2025-62001/index.md)","id":"CVE-2025-62001","markdown":"https://insights.sbomify.com/CVE-2025-62001/index.md","name":"CVE-2025-62001","record":{"aliases":["GHSA-mx9q-6x2g-xj7c"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ransomware containment software","requires_auth":"low_privilege","summary":"An authenticated attacker can bypass ransomware monitoring by renaming directories to match hardcoded exclusion patterns, requiring a software update.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"ransomware_containment","vendor":"bullwall"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-420","name":"Unprotected Alternate Channel"}],"description":"BullWall Ransomware Containment supports configurable file and directory exclusions such as '$RECYCLE.BIN' to balance monitoring scope and performance. Certain exclusion patterns could allow an authenticated attacker to rename directories in a way that avoids monitoring. Fixed in 4.6.1.14 and 5.0.0.42, which remove hardcoded exclusion behavior and exposes exclusion handling as configurable settings.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"BullWall Ransomware Containment hard-coded folder exclusions","id":"CVE-2025-62001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"BullWall Ransomware Containment file count detection bypass","id":"CVE-2025-62002"},"packages":[],"prev":{"headline":"BullWall Ransomware Containment incomplete file inspection","id":"CVE-2025-62000"},"products":["Ransomware Containment"],"published":"2025-12-18","related":[{"cvss_score":6.9,"headline":"BullWall Ransomware Containment incomplete file inspection","id":"CVE-2025-62000","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":5.3,"headline":"BullWall Ransomware Containment file count detection bypass","id":"CVE-2025-62002","kev_date_added":null,"published":"2025-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-01-15","vendors":["BullWall"]},"summary":"An authenticated attacker can bypass ransomware monitoring by renaming directories to match hardcoded exclusion patterns, requiring a software update.","url":"https://insights.sbomify.com/CVE-2025-62001/"}