CVE-2026-46673: Russh CryptoVec Memory Safety Vulnerability

Technical summary

CryptoVec, a specialized buffer class in Russh, implements custom memory allocation and locking to handle cryptographic material securely. The vulnerability exists in three interconnected issues: unchecked capacity growth (allowing integer overflows or excessive allocations), unchecked length arithmetic (permitting out-of-bounds operations), and unsafe allocation/locking paths (bypassing safety guarantees). In pre-0.58.0 versions, untrusted SSH transport and compression data fed directly into CryptoVec, exposing the library to remote exploitation. Even in later versions (0.58.0 through 0.60.2), local SSH agent peers can still inject attacker-controlled frame lengths that trigger unsafe buffer expansion before proper validation occurs. This represents a classic use-after-free or heap corruption risk in unsafe Rust code paths.

Business impact

Organizations using Russh in production SSH servers or agents face availability risk. Unauthenticated remote attackers can trigger out-of-memory conditions or memory corruption in pre-0.58.0 deployments, causing service crashes. Even current-version deployments (0.58.0–0.60.2) remain vulnerable to local privilege escalation or denial of service via compromised SSH agents. For any software embedding Russh for secure shell automation, remote access, or cryptographic operations, an unpatched instance becomes a vector for disruption or potential lateral movement in a defense-in-depth scenario.

Affected systems

Russh versions prior to 0.60.3 are affected. The vulnerability's attack surface scales with deployment context: pre-0.58.0 versions accept remote SSH traffic; versions 0.58.0 through 0.60.2 remain vulnerable to local SSH agent manipulation. Any application or service that vendors Russh as a dependency—including custom SSH automation tools, secure gateways, remote access solutions, and cryptographic middleware—should be inventoried and evaluated. Rust-based projects in embedded systems, IoT devices, or cloud infrastructure are particularly common consumers of this library.

Exploitability

The CVSS:3.1 score of 7.5 (HIGH) reflects network accessibility and no authentication requirement for remote variants. Pre-0.58.0 versions are directly exploitable by unauthenticated SSH clients sending crafted frame data. Later versions require local access (SSH agent context), raising the bar but not eliminating risk in multi-tenant or shared-system scenarios. No exploit code is currently public, and the vulnerability is not yet listed on CISA's Known Exploited Vulnerabilities catalog, but the simplicity of triggering memory exhaustion makes weaponization straightforward once proof-of-concept tooling emerges. The flaw does not require user interaction.

Remediation

Immediate action: upgrade Russh to version 0.60.3 or later. This patch hardens CryptoVec's capacity checks, validates length arithmetic before allocation, and removes or guards unsafe code paths. For organizations unable to upgrade immediately, network-level mitigation is limited (SSH traffic is encrypted), but restricting SSH connectivity to trusted sources and monitoring local agent behavior can reduce remote and local attack surface. Legacy applications still on pre-0.58.0 should be prioritized for urgent patching due to remote exploitability.

Patch guidance

Verify your application's Cargo.toml or equivalent dependency manifest for the current Russh version. Update the Russh crate to 0.60.3 or later—this is a security patch with no breaking changes expected. Test in a staging environment first, particularly if you have custom SSH server logic or agent integrations. After deployment, confirm the patched version is running (e.g., query runtime dependency versions or logs). If Russh is vendored indirectly through another library, trace the dependency chain and request that upstream project update; do not assume transitivity will auto-resolve.

Detection guidance

Monitor SSH servers for unexpected memory growth, crashes, or out-of-memory errors, especially surrounding SSH agent connections or transport layer activity. Unpatched systems may show erratic buffer allocation patterns in profilers or core dumps. Network-based detection is challenging due to encryption, but SSH connection logs with abnormal frame sizes or rapid session cycling may warrant investigation. Audit Cargo.lock files and build artifacts to confirm Russh version in production. Correlate any observed availability incidents with SSH activity timelines.

Why prioritize this

This vulnerability warrants urgent attention due to its HIGH severity, network accessibility in older versions, and potential for widespread impact across Rust-based SSH infrastructure. Although not yet exploited in the wild (per KEV status), the simplicity of exploitation and the ubiquity of SSH in cloud, DevOps, and automation contexts make pre-0.58.0 deployments critical risks. Even current-version systems require prompt patching to eliminate local vector exposure.

Risk score, explained

CVSS 7.5 reflects high base severity: network attack vector (AV:N), low complexity (AC:L), no privilege or user interaction required (PR:N, UI:N), but scope unchanged and no confidentiality or integrity impact—only availability (A:H) is compromised. The score accurately captures denial-of-service risk via memory exhaustion; it does not account for potential memory corruption leading to code execution, which may be underscored in certain advanced scenarios. The lack of KEV listing suggests no known active exploitation, reducing temporal pressure slightly but not justifying delay.

Frequently asked questions