Rust advisories / crate
Security history · russh · data from Oct 24, 2026
Is russh safe to use? Its security history
VerdictNo open advisories. 23 past vulnerabilities were fixed; use 0.60.3 or newer to be clear of all of them.
Every advisory, newest first
- VulnerabilityGHSA-4wc5-f2rc-q74m · 2026-10-19russh: Unbounded memory allocation in agent protocol server via crafted constraint records
- VulnerabilityGHSA-j7h2-66j4-ghjf · 2026-10-19A russh SSH server accepts a publickey authentication whose signature uses a different algorithm than the one named in the request
- VulnerabilityGHSA-35g8-35p8-c8fw · 2026-09-30Russh: Unbounded memory exhaustion via CHANNEL_OPEN flood during a client-stalled rekey
- VulnerabilityGHSA-p8qx-h547-fjw9 · 2026-09-30russh: negotiating a MAC-requiring block cipher (CTR/CBC) with mac=none causes a slice-index-out-of-range panic
- VulnerabilityGHSA-47hw-gvq5-r2gm · 2026-09-30russh: Client-side channel-scoped Handler callbacks fire for channel IDs the client never opened
- VulnerabilityGHSA-w3jg-pjxf-73p4 · 2026-09-30Russh: Missing X25519 zero-point validation in hybrid ML-KEM key exchange
- VulnerabilityGHSA-g6xm-f9xp-qq35 · 2026-09-30Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path
- VulnerabilityGHSA-m65r-rprj-r5rg · 2026-08-03Russh: Channel-scoped server callbacks can be reached without an open channel
- VulnerabilityGHSA-g9hv-x236-4qp3 · 2026-07-24Russh: client wrong-length X25519 `clone_from_slice` panic (pre-auth DoS)
- VulnerabilityGHSA-cqjc-rmpq-xprq · 2026-07-24Russh: Post-auth remote panic via pty-req with more than 130 terminal-mode records
- VulnerabilityGHSA-5xvq-cp9x-6p6r · 2026-07-24Russh: Pre-auth remote panic via all-zero Curve25519 peer public value (encode_mpint OOB)
- VulnerabilityGHSA-4r3c-5hpg-58qr · 2026-06-11Russh SSH message fields were decoded through allocation-first parsers before field-specific bounds
- VulnerabilityGHSA-76r6-x97p-67vr · 2026-06-11Russh: SSH identification parsing accepted non-canonical client banners and did not bound pre-banner input
- VulnerabilityGHSA-g9g7-5cgw-6v28 · 2026-06-11Russh: Unchecked keyboard-interactive prompt count in client auth path
- VulnerabilityGHSA-hpv4-5h6f-wqr3 · 2026-05-29russh server userauth state is not reset when authentication principal changes
- VulnerabilityGHSA-wwx6-x28x-8259 · 2026-05-29russh: Post-decompression SSH packet size was not bounded, allowing remote oversized compressed packets
- Vulnerability HighRUSTSEC-2026-0154 · 2026-05-15Unbounded 32-bit allocation
- VulnerabilityGHSA-f5v4-2wr6-hqmg · 2026-04-24russh has pre-auth DoS via unbounded allocation in its keyboard-interactive auth handler
- VulnerabilityGHSA-h5rc-j5f5-3gcm · 2025-08-04russh is missing overflow checks during channel windows adjust
- VulnerabilityGHSA-vgvv-x7xg-6cqg · 2024-08-14Russh has an OOM Denial of Service due to allocation of untrusted amount
- VulnerabilityGHSA-45x7-px36-x8w8 · 2023-12-18Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin
- VulnerabilityGHSA-cqvm-j2r2-hwpg · 2023-03-17russh may use insecure Diffie-Hellman keys
- VulnerabilityGHSA-cqvm-j2r2-hwpg · 2023-03-17russh may use insecure Diffie-Hellman keys
Check your version
Run cargo tree -i russh to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?