{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61303 exists.","fix":"No fix has been published for CVE-2025-61303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61303 is a critical denial of service vulnerability in n/a, published on 20 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-61303 and fix it if it is affected.\n\nWhat it is: CVE-2025-61303 is a critical denial of service vulnerability in n/a, published on 20 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61303 exists.\n\nAffected product: n/a. 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-61303/ (Markdown: https://insights.sbomify.com/CVE-2025-61303/index.md)","id":"CVE-2025-61303","markdown":"https://insights.sbomify.com/CVE-2025-61303/index.md","name":"CVE-2025-61303","record":{"aliases":["GHSA-8rm8-qf3c-q22g"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Malware analysis sandbox","requires_auth":"none","summary":"Attackers can evade malware detection and disrupt analysis by spawning recursive child processes, causing resource exhaustion in the sandbox.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Hatching Triage Sandbox Windows 10 build 2004 (2025-08-14) and Windows 10 LTSC 2021(2025-08-14) contains a vulnerability in its Windows behavioral analysis engine that allows a submitted malware sample to evade detection and cause denial-of-analysis. The vulnerability is triggered when a sample recursively spawns a large number of child processes, generating high log volume and exhausting system resources. As a result, key malicious behavior, including PowerShell execution and reverse shell activity, may not be recorded or reported, misleading analysts and compromising the integrity and availability of sandboxed analysis results.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-10","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-10T14:54:26Z","kind":"github_poc","ref":"https://github.com/eGkritsis/CVE-2025-61303","stars":2,"title":"Critical Vulnerability (9.8) - RecordedFuture Triage dynamic analysis engine can fail to record malicious behavior when samples produce very high-volume recursive process forking, causing inconsistent or missing behavioral reports."}],"tier":"weaponised"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2025-61303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2025-61304"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-61301"},"products":["n/a"],"published":"2025-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"Attackers can evade malware detection and disrupt analysis by spawning recursive child processes, causing resource exhaustion in the sandbox.","url":"https://insights.sbomify.com/CVE-2025-61303/"}