Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

russh-cryptovec

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 7.5crates.ioPublished

    Russh: Unchecked CryptoVec allocation and growth handling is reachable

    CVE-2026-46673 · GHSA-g9f8-wqj9-fjw5

    Affected
    • crates.io russh-cryptovec <= 0.60.2
    Fixed in
    0.60.3· Vendor fix available
    Issue
    Title Unchecked CryptoVec allocation and growth handling was reachable from local agent inputs in current russh releases and from remote SSH traffic in historical pre-0.58.0 releases Summary CryptoVec used unchecked capacity growth, unchecked length arithmetic, and unsafe allocation/locking paths. In current russh releases, local SSH agent peers could still feed attacker-controlled frame lengths into buffer growth before validation. In older russh releases before 0.58.0, remote SSH traffic also reached CryptoVec through transport and compression buffers. Details The underlying unsafe paths were in CryptoVec: - cryptovec/src/cryptovec.rs - unchecked capacity growth - unchecked length arithmetic in growth callers - raw allocation and reallocation paths coupled to those sizes - cryptovec/src/platform/unix.rs - mlock / munlock previously accepted zero-length calls and performed null-pointer validation inside the unsafe OS-call path There are two relevant reachability stories: 1. current…

    Recommended action: Upgrade to 0.60.3 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 →