Skip to main content
VulnerabilityPublished Updated

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

Affects thread-amountSource GCVE Database

0
Compare
Authoritative record:CVE-2025-65947· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 0.2.2 soon.

Data as of 19 Nov 2026, 02:47 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 0.2.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade thread-amount to 0.2.2.

Affected software

ProductAffectedFixed in
crates.iothread-amountAffected
  • <0.2.2
Fixed in
  • 0.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to thread-amount version 0.2.2 or later, where the resource leaks on Windows and macOS/iOS have been fixed. No other mitigation is required as the fix addresses the root cause.

Description

The thread-amount crate versions prior to 0.2.2 contain resource leaks on Windows and macOS/iOS platforms when querying thread counts. On Windows, the function fails to close handles returned by CreateToolhelp32Snapshot, causing handle leaks. On macOS/iOS, memory allocated by task_threads is not deallocated, causing memory leaks. Long-running applications using this crate to periodically check thread counts may crash due to resource exhaustion. A fix is available in version 0.2.2.

References

Community reviews

Loading reviews…