# CVE-2025-61303: Denial of service in n/a

> Attackers can evade malware detection and disrupt analysis by spawning recursive child processes, causing resource exhaustion in the sandbox.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-8rm8-qf3c-q22g

## What is CVE-2025-61303?

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.

### Official 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-61303?


## How do I fix CVE-2025-61303?

No fix has been published for CVE-2025-61303 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61303 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61303 exists.

Public exploit code:

- 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. (github_poc): https://github.com/eGkritsis/CVE-2025-61303

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61303 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61303 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61303/ (Markdown: https://insights.sbomify.com/CVE-2025-61303/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61303
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61303
- OSV: https://osv.dev/vulnerability/CVE-2025-61303

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61303/
Summaries are generated and may contain mistakes; the official description above is the record.