https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T08:32:01.262432+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2026-46673 CVE-2026-46673 — Russh: Unchecked CryptoVec allocation and growth handling is reachable from local agent inputs in current russh release… 2026-10-03T08:32:01.264162+00:00

Affected: Eugeny russh

Russh is a Rust SSH client & server library. Prior to version 0.60.3, 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. This issue has been patched in version 0.60.3.

 https://cve.radiocsirt.org/vuln/ghsa-g9f8-wqj9-fjw5 GHSA-g9f8-wqj9-fjw5 — Russh: Unchecked CryptoVec allocation and growth handling is reachable 2026-10-03T08:32:01.264216+00:00

Affected: crates.io: russh-cryptovec, crates.io: russh

### 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 local reachability in `russh`

- `russh/src/keys/agent/client.rs` - `AgentClient::read_response()` read a peer-supplied `u32` length and then resized `self.buf` to that value before reading the payload - `russh/src/keys/agent/server.rs` - `Connection::run()` read a peer-supplied `u32` length and then resized `self.buf` to that value before reading the payload

This is the path that still existed in current `0.60.x` releases before the fix,…