# CVE-2025-65947: thread-amount DoS — Fixed in 0.2.2

🦀 crates.io

Not in CISA KEV

# CVE-2025-65947 — thread-amount

[Fix: jzeuzs/thread-amount@28860d4](https://github.com/jzeuzs/thread-amount/commit/28860d4a38286609cb884c13b5b7941edc2390e5)

CVE-2025-65947 is a Uncontrolled Resource Consumption vulnerability in thread-amount. A fix is available for thread-amount — see the affected versions and patch details below.

thread-amount is Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS

Also known as[GHSA-jf9p-2fv9-2jp2](/vulnerability/GHSA-jf9p-2fv9-2jp2)RUSTSEC-2025-0125

Published

Nov 21, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-65947.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.4%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

0.00%0.29%0.58%0.87%0.1%0.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

🦀`thread-amount`

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

## Description

Affected versions of this crate contain resource leaks when querying thread counts on Windows and Apple platforms.

#### Windows

The `thread_amount` function calls `CreateToolhelp32Snapshot` but fails to close the returned `HANDLE` using `CloseHandle`. Repeated calls to this function will cause the handle count of the process to grow indefinitely, eventually leading to system instability or process termination when the handle limit is reached.

#### macOS / iOS

The `thread_amount` function calls `task_threads` (via Mach kernel APIs) which allocates memory for the thread list. The function fails to deallocate this memory using `vm_deallocate`. Repeated calls will result in a steady memory leak, eventually causing the process to be killed by the OOM (Out of Memory) killer.

#### Impact

Long-running applications (such as servers, daemons, or monitoring tools) that use this crate to periodically check thread counts will eventually crash due to resource exhaustion.

#### Resources

-   [https://github.com/jzeuzs/thread-amount/pull/29](https://github.com/jzeuzs/thread-amount/pull/29)

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

🦀crates.io

`thread-amount` 

all versions

0.2.2`cargo update -p thread-amount --precise 0.2.2`

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thread-amount, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update thread-amount to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-65947 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
    

## Frequently Asked Questions

Affected versions of this crate contain resource leaks when querying thread counts on Windows and Apple platforms. ### Windows The \`thread\_amount\` function calls \`CreateToolhelp32Snapshot\` but fails to close the returned \`HANDLE\` using \`CloseHandle\`. Repeated calls to this function will cause the handle count of the process to grow indefinitely, eventually leading to system instability or process termination when the handle limit is reached. ### macOS / iOS The \`thread\_amount\` function calls \`task\_threads\` (via Mach kernel APIs) which allocates memory for the thread list. The function fails

O3 Security · Impact-Aware SCA

### Is CVE-2025-65947 in your dependencies?

Find it across crates.io, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)