CVE-2026-111062Low 2.3A russh SSH server accepts a publickey authentication whose signature uses a different algorithm than the one named in the request0.4%
CVE-2026-116794High 8.3russh: Agent server never calls `Agent::confirm`, so keys added with the confirm constraint (`ssh-add -c`) sign without confirmation0.2%
CVE-2026-68930Medium 6.5Russh: Channel-scoped server callbacks can be reached without an open channel0.4%
CVE-2026-48110High 7.5Russh: SSH message fields were decoded through allocation-first parsers before field-specific bounds0.4%
CVE-2026-48108Medium 5.3Russh: SSH identification parsing accepted non-canonical client banners and did not bound pre-banner input0.3%
CVE-2026-48107Medium 6.5Russh: Unchecked keyboard-interactive prompt count in client auth path0.2%
CVE-2026-46705Medium 5.3russh server userauth state is not reset when authentication principal changes0.2%
CVE-2026-46702High 7.5Russh: Post-decompression SSH packet size was not bounded, allowing remote oversized compressed packets0.3%
CVE-2026-46673High 7.5Russh: Unchecked CryptoVec allocation and growth handling is reachable from local agent inputs in current russh releases and from remote SSH traffic in historical pre-0.58.0 releases0.3%
CVE-2026-42189High 7.5Russh: Pre-auth DoS via unbounded allocation in keyboard-interactive auth0.5%
CVE-2025-54804Medium 6.5Russh is missing an overflow check during channel windows adjust0.4%
CVE-2024-43410High 7.5Russh has an OOM Denial of Service due to allocation of untrusted amount0.9%