CVE-2026-102825: Russh Remote Code Execution Vulnerability

LOW
Advisory Identifier: GHSA-g6xm-f9xp-qq35
CVSS 3.7
CWE-307
Published
Advisory Summary

CVE-2026-102825 is a LOW (CVSS 3.7) remote code execution vulnerability (CWE-307: Improper Restriction of Excessive Authentication Attempts) affecting Russh libraries in the crates.io ecosystem. The issue involves configured server auth-attempt cap is not enforced in the userauth_request runtime path. Remediation is available by upgrading affected packages to version 0.62.6.

CVE-2026-102825 at a Glance

CVE Identifier CVE-2026-102825
GHSA Identifier GHSA-g6xm-f9xp-qq35
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-307: Improper Restriction of Excessive Authentication Attempts
Affected Product Russh
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-102825

To remediate this vulnerability, upgrade all affected Russh dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

russh fixed: 0.62.6
Upgrade russh to 0.62.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for russh

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-102825, inspect your project dependencies for Russh:

inspect dependencies for russh

Analyze the terminal output to locate any version of Russh in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.62.6), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts, where the product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. In Russh, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Details #### Affected versions and vulnerable location - Confirmed present on default branch `main` at HEAD `0089c89c94753bebbec12b956c07a1cd38740379`. - Crate version at HEAD: `0.62.4`. - Vulnerable locations on current default branch: - `russh/src/server/mod.rs:91` (`pub max_auth_attempts: usize`) - `russh/src/server/mod.rs:121` (default `max_auth_attempts: 10`) - `russh/src/server/encrypted.rs:89` (`USERAUTH_REQUEST` dispatch into auth handler path) - `russh/src/server/encrypted.rs:98` (`self.common.auth_attempts += 1`) - `russh/src/server/encrypted.rs:53` (only runtime read of `auth_attempts`, used for initial reject timing, not attempt limiting) - Default-branch history check did not show a newer merged commit adding enforcement against `config.max_auth_attempts`. #### Reachability trace verified 1. Entry point: exported server API `server::run_stream` in `russh/src/server/mod.rs:1049`. 2. Session run loop in `russh/src/server/session.rs` processes incoming packets and calls `reply(...)` (`server/session.rs:725`). 3. `reply` forwards encrypted packets to `session.server_read_encrypted(...)` (`server/mod.rs:1221`). 4. `server_read_encrypted` routes `USERAUTH_REQUEST` to `enc.server_read_auth_request(...)` (`server/encrypted.rs:89`). 5. On each request, `self.common.auth_attempts += 1` executes (`server/encrypted.rs:98`). 6. No comparison against `self.common.config.max_auth_attempts` is present in this runtime flow. ### PoC #### Reproduction steps and observed output I did not run a full server process in this environment because Rust tooling is unavailable. I verified the issue from source and command output on the audited tree. 1. Show where `max_auth_attempts` appears: ```bash rtk rg -n "max_auth_attempts" .scratch/russh/russh/src/server/mod.rs .scratch/russh/russh/src/server/encrypted.rs .scratch/russh/russh/src/server/session.rs ``` Observed: ```text .scratch/russh/russh/src/server/mod.rs:91: pub max_auth_attempts: usize, .scratch/russh/russh/src/server/mod.rs:121: max_auth_attempts: 10, .scratch/russh/russh/src/server/mod.rs:148: .field("max_auth_attempts", &self.max_auth_attempts) ``` 2. Show runtime auth-attempt handling: ```bash rtk rg -n "auth_attempts == 0|auth_attempts \\+= 1" .scratch/russh/russh/src/server/encrypted.rs ``` Observed: ```text 53: let initial_none_rejection_wait_until = if self.common.auth_attempts == 0 { 98: self.common.auth_attempts += 1; ``` 3. Show production entrypoint-to-auth path references: ```bash rtk rg -n "pub async fn run_stream|match reply\\(|server_read_encrypted\\(|server_read_auth_request\\(" .scratch/russh/russh/src/server/mod.rs .scratch/russh/russh/src/server/session.rs .scratch/russh/russh/src/server/encrypted.rs ``` Observed: ```text .scratch/russh/russh/src/server/encrypted.rs:89: enc.server_read_auth_request( .scratch/russh/russh/src/server/session.rs:725: match reply(&mut self, &mut handler, &mut pkt).await { .scratch/russh/russh/src/server/mod.rs:1049:pub async fn run_stream<H, R>( .scratch/russh/russh/src/server/mod.rs:1221: session.server_read_encrypted(handler, pkt).await ``` 4. Toolchain check: ```bash cargo --version ``` Observed: ```text /bin/bash: line 1: cargo: command not found ``` ### Impact #### Attacker model - Attacker: unauthenticated remote client with TCP reachability to a russh-backed SSH service. - Preconditions: deployer expects `server::Config.max_auth_attempts` to cap attempts. - Impact: repeated `USERAUTH_REQUEST` attempts continue for a single connection beyond configured limit, increasing online guessing opportunity and backend auth workload. ### Suggested fix Enforce `max_auth_attempts` in the `USERAUTH_REQUEST` branch before invoking auth-method handlers, and fail closed once threshold is reached. Concrete patch direction in `russh/src/server/encrypted.rs`: ```rust if self.common.config.max_auth_attempts > 0 && self.common.auth_attempts >= self.common.config.max_auth_attempts { self.common.disconnect( Disconnect::NoMoreAuthMethodsAvailable, "Too many authentication attempts", "", )?; return Ok(()); } ``` ### How it was found and a note on tooling The researcher synthesized three lens outputs, then revalidated each claim against current `main`: source presence and commit history, advisory overlap checks in both GitHub advisories and OSV, entrypoint-to-sink reachability, attacker-model realism, and execution-claim integrity. The researcher used `gh`, `git`, `rg`, and direct source inspection under `.scratch/russh`. Because Rust tooling is unavailable in this worker, this report is intentionally marked `source-only`. AI assistance was used while investigating this and while drafting this report. The finding was verified by reading the cited code at HEAD. The vulnerability was not executed it, and that limit is stated plainly above rather than left implied. Credits: arpitjain099.

CVE-2026-102825 Affected Russh Versions

1 component(s)
Fixed Versions:
0.62.6
Product / Package Ecosystem Affected Versions Fixed Version
russh
crates.io
< 0.62.6
0.62.6

References

Frequently Asked Questions

What is CVE-2026-102825?
CVE-2026-102825 is a security vulnerability in Russh involving Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path under CWE-307: Improper Restriction of Excessive Authentication Attempts.
Which Russh versions are affected?
Affected versions include releases prior to 0.62.6 across affected packages: russh.
What version fixes CVE-2026-102825?
Upgrading to 0.62.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is russh affected?
Yes, russh is affected in releases prior to 0.62.6. Upgrade your dependency to 0.62.6 or later.
What is the CVSS score of CVE-2026-102825?
CVE-2026-102825 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-102825?
CVE-2026-102825 is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts (The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.).
How can I check crates.io dependencies for CVE-2026-102825?
Run the dependency tree command: 'inspect dependencies for russh'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g6xm-f9xp-qq35",
  "modified" : "2026-09-30T23:26:17Z",
  "published" : "2026-09-30T23:26:17Z",
  "aliases" : [ "CVE-2026-102825" ],
  "summary" : "Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path",
  "details" : "### Details\n\n#### Affected versions and vulnerable location\n\n- Confirmed present on default branch `main` at HEAD `0089c89c94753bebbec12b956c07a1cd38740379`.\n- Crate version at HEAD: `0.62.4`.\n- Vulnerable locations on current default branch:\n  - `russh/src/server/mod.rs:91` (`pub max_auth_attempts: usize`)\n  - `russh/src/server/mod.rs:121` (default `max_auth_attempts: 10`)\n  - `russh/src/server/encrypted.rs:89` (`USERAUTH_REQUEST` dispatch into auth handler path)\n  - `russh/src/server/encrypted.rs:98` (`self.common.auth_attempts += 1`)\n  - `russh/src/server/encrypted.rs:53` (only runtime read of `auth_attempts`, used for initial reject timing, not attempt limiting)\n- Default-branch history check did not show a newer merged commit adding enforcement against `config.max_auth_attempts`.\n\n#### Reachability trace verified\n\n1. Entry point: exported server API `server::run_stream` in `russh/src/server/mod.rs:1049`.\n2. Session run loop in `russh/src/server/session.rs` processes incoming packets and calls `reply(...)` (`server/session.rs:725`).\n3. `reply` forwards encrypted packets to `session.server_read_encrypted(...)` (`server/mod.rs:1221`).\n4. `server_read_encrypted` routes `USERAUTH_REQUEST` to `enc.server_read_auth_request(...)` (`server/encrypted.rs:89`).\n5. On each request, `self.common.auth_attempts += 1` executes (`server/encrypted.rs:98`).\n6. No comparison against `self.common.config.max_auth_attempts` is present in this runtime flow.\n\n### PoC\n\n#### Reproduction steps and observed output\n\nI did not run a full server process in this environment because Rust tooling is unavailable. I verified the issue from source and command output on the audited tree.\n\n1. Show where `max_auth_attempts` appears:\n\n```bash\nrtk rg -n \"max_auth_attempts\" .scratch/russh/russh/src/server/mod.rs .scratch/russh/russh/src/server/encrypted.rs .scratch/russh/russh/src/server/session.rs\n```\n\nObserved:\n\n```text\n.scratch/russh/russh/src/server/mod.rs:91:    pub max_auth_attempts: usize,\n.scratch/russh/russh/src/server/mod.rs:121:            max_auth_attempts: 10,\n.scratch/russh/russh/src/server/mod.rs:148:            .field(\"max_auth_attempts\", &self.max_auth_attempts)\n```\n\n2. Show runtime auth-attempt handling:\n\n```bash\nrtk rg -n \"auth_attempts == 0|auth_attempts \\\\+= 1\" .scratch/russh/russh/src/server/encrypted.rs\n```\n\nObserved:\n\n```text\n53:        let initial_none_rejection_wait_until = if self.common.auth_attempts == 0 {\n98:                self.common.auth_attempts += 1;\n```\n\n3. Show production entrypoint-to-auth path references:\n\n```bash\nrtk rg -n \"pub async fn run_stream|match reply\\\\(|server_read_encrypted\\\\(|server_read_auth_request\\\\(\" .scratch/russh/russh/src/server/mod.rs .scratch/russh/russh/src/server/session.rs .scratch/russh/russh/src/server/encrypted.rs\n```\n\nObserved:\n\n```text\n.scratch/russh/russh/src/server/encrypted.rs:89:                enc.server_read_auth_request(\n.scratch/russh/russh/src/server/session.rs:725:                            match reply(&mut self, &mut handler, &mut pkt).await {\n.scratch/russh/russh/src/server/mod.rs:1049:pub async fn run_stream<H, R>(\n.scratch/russh/russh/src/server/mod.rs:1221:    session.server_read_encrypted(handler, pkt).await\n```\n\n4. Toolchain check:\n\n```bash\ncargo --version\n```\n\nObserved:\n\n```text\n/bin/bash: line 1: cargo: command not found\n```\n\n### Impact\n\n#### Attacker model\n\n- Attacker: unauthenticated remote client with TCP reachability to a russh-backed SSH service.\n- Preconditions: deployer expects `server::Config.max_auth_attempts` to cap attempts.\n- Impact: repeated `USERAUTH_REQUEST` attempts continue for a single connection beyond configured limit, increasing online guessing opportunity and backend auth workload.\n\n### Suggested fix\n\nEnforce `max_auth_attempts` in the `USERAUTH_REQUEST` branch before invoking auth-method handlers, and fail closed once threshold is reached.\n\nConcrete patch direction in `russh/src/server/encrypted.rs`:\n\n```rust\nif self.common.config.max_auth_attempts > 0\n    && self.common.auth_attempts >= self.common.config.max_auth_attempts\n{\n    self.common.disconnect(\n        Disconnect::NoMoreAuthMethodsAvailable,\n        \"Too many authentication attempts\",\n        \"\",\n    )?;\n    return Ok(());\n}\n```\n\n### How it was found and a note on tooling\n\nThe researcher synthesized three lens outputs, then revalidated each claim against current `main`: source presence and commit history, advisory overlap checks in both GitHub advisories and OSV, entrypoint-to-sink reachability, attacker-model realism, and execution-claim integrity. The researcher used `gh`, `git`, `rg`, and direct source inspection under `.scratch/russh`. Because Rust tooling is unavailable in this worker, this report is intentionally marked `source-only`.\n\nAI assistance was used while investigating this and while drafting this report. The finding was verified by reading the cited code at HEAD. The vulnerability was not executed it, and that limit is stated plainly above rather than left implied.\n\nCredits: arpitjain099.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "russh"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.62.6"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.62.5"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Eugeny/russh/security/advisories/GHSA-g6xm-f9xp-qq35"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-102825"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Eugeny/russh/commit/f8fd0b11a393364dc7f01a182482d86adafdd653"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Eugeny/russh"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Eugeny/russh/releases/tag/v0.62.6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-307" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-30T23:26:17Z",
    "nvd_published_at" : "2026-09-29T19:17:24Z"
  }
}