russh-cryptovec
Affected
- introduced
0.0.0-0, fixed0.60.3(semver)
Fixed versions
0.60.3
Fix
- Fixed version
0.60.3cargo update -p russh-cryptovec --precise 0.60.3
Advisory
Also known as: CVE-2026-46673, GHSA-g9f8-wqj9-fjw5, RUSTSEC-2026-0154
Unchecked CryptoVec allocation and growth handling
CryptoVec used unchecked capacity growth, unchecked length arithmetic, and
unsafe allocation and locking paths. In affected russh releases,
attacker-controlled input could reach these code paths through buffer resizing
operations.
Two affected reachability paths were identified:
AgentClient::read_responseagent::server::Connection::runCryptoVec was also used for non-secret transport and compression buffers, allowing remote SSH traffic to trigger CryptoVec growth through:These remote paths were removed in 0.58.0 when CryptoVec stopped being used
for those buffers.
Under constrained memory conditions, historical russh versions prior to0.58.0 can abort the process when remote compressed payload expansion causes
allocation failure in CryptoVec. This was reproduced through the compression
path and resulted in process termination in the Unix allocation/locking
implementation after null pointer allocation failure.
For current affected releases, oversized local SSH agent frame lengths could
trigger untrusted-input-driven buffer growth prior to validation.
No practical remote code execution, integrity or confidentiality impact has
been demonstrated.
Fixed by validating CryptoVec growth operations and rejecting oversized SSH
agent frame lengths before buffer allocation.
High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
0.0.0-0, fixed 0.60.3 (semver)0.60.3
0.60.3cargo update -p russh-cryptovec --precise 0.60.3Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0