CVE-2025-65947 json
thread-amount is Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS
published 2025-11-21 11 mo ago modified 2026-10-18 21 d ago also GHSA-jf9p-2fv9-2jp2 , RUSTSEC-2025-0125 , EUVD-2025-198497
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
thread-amount is a tool that gets the amount of threads in the current process. Prior to version 0.2.2, there are resource leaks when querying thread counts on Windows and Apple platforms. In Windows platforms, 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. In Apple platforms, 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. This issue has been patched in version 0.2.2.
Patch / fix
- crates.io thread-amount 0.2.2
- github.com/jzeuzs/thread-amount@28860d4 commit
- github.com/jzeuzs/thread-amount#29 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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 |
| CNA | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | thread-amount | <0.2.2 >=0.0.0-0, <0.2.2 |
0.2.2 |
Affected products
- jzeuzs thread-amount
Classification
References
-
github.com
/jzeuzs/thread-amount/pull/29
web
-
github.com
/jzeuzs/thread-amount/commit/28860d4a38286609cb884c13b5b7941edc2390e5
web
-
github.com
/jzeuzs/thread-amount/security/advisories/GHSA-jf9p-2fv9-2jp2
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-65947
advisory
-
github.com
/jzeuzs/thread-amount
package
-
rustsec.org
/advisories/RUSTSEC-2025-0125.html
web, advisory
-
crates.io
/crates/thread-amount
package
Sources
- CVE List CVE-2025-65947
- GitHub Advisory GHSA-jf9p-2fv9-2jp2
- NVD CVE-2025-65947
- OSV RUSTSEC-2025-0125
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.