Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

thread-amount

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7crates.ioPublished

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

    CVE-2025-65947 · GHSA-jf9p-2fv9-2jp2

    Affected
    • crates.io thread-amount < 0.2.2
    Fixed in
    0.2.2· Vendor fix available
    Issue
    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

    Recommended action: Upgrade to 0.2.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →