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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-65947: 0.37% estimated exploitation activity in the next 30 days; percentile 31.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected versions of this crate contain resource leaks when querying thread counts on Windows and Apple platforms. Windows The threadamount 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 threadamount function calls taskthreads (via Mach kernel APIs) which allocates memory for the thread list. The function fails to deallocate this memory using vmdeallocate. 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

Published by the source

21 Nov 2025, 18:19 UTC

Last modified by the source

27 Nov 2025, 07:53 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jf9p-2fv9-2jp2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-65947

Advisory: thread-amount Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS
IDs: CVE-2025-65947, GHSA-jf9p-2fv9-2jp2
Record: https://patchnext.com/advisories/cve-2025-65947 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: thread-amount 0.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io thread-amount: affected < 0.2.2; fixed in 0.2.2

## Suggested inspection (read-only)
- crates.io thread-amount: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on thread-amount.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jf9p-2fv9-2jp2 (GitHub-reviewed advisory GHSA-jf9p-2fv9-2jp2 lists affected ranges: crates.io thread-amount >=0 <0.2.2)

Commands are suggestions: review each one before running it.