Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-102825

Published

Russh is a Rust SSH client and server library. Prior to 0.62.6, the USERAUTH_REQUEST path reached from server::run_stream in russh/src/server/encrypted.rs increments self.common.auth_attempts but never compares it with server::Config.max_auth_attempts. An unauthenticated remote client can continue submitting authentication requests on one connection beyond the configured cap, bypassing the deployment's attempt-limiting policy and increasing online guessing opportunity and backend authentication workload. This issue is fixed in version 0.62.6.

Source published
29 Sep 2026 18:31:32 UTC
Source modified
30 Sep 2026 19:29:26 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

euvd · EUVD-2026-89365

Published

Russh is a Rust SSH client and server library. Prior to 0.62.6, the USERAUTH_REQUEST path reached from server::run_stream in russh/src/server/encrypted.rs increments self.common.auth_attempts but never compares it with server::Config.max_auth_attempts. An unauthenticated remote client can continue submitting authentication requests on one connection beyond the configured cap, bypassing the deployment's attempt-limiting policy and increasing online guessing opportunity and backend authentication workload. This issue is fixed in version 0.62.6.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 29, 2026, 6:31:32 PM

dateUpdated: Sep 30, 2026, 7:29:26 PM

1 related source bulletins · separate from aliases

RHSA-2026:74586: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

CVE-2026-102821 · CVE-2026-102823 · CVE-2026-102824 · CVE-2026-102825

Source published
Sep 29, 2026, 6:31:32 PM (timezone not stated)
Source modified
Sep 30, 2026, 7:29:26 PM (timezone not stated)
Saved here
15 Nov 2026 06:32:53 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd · CVE-2026-102825

Published

Russh is a Rust SSH client and server library. Prior to 0.62.6, the USERAUTH_REQUEST path reached from server::run_stream in russh/src/server/encrypted.rs increments self.common.auth_attempts but never compares it with server::Config.max_auth_attempts. An unauthenticated remote client can continue submitting authentication requests on one connection beyond the configured cap, bypassing the deployment's attempt-limiting policy and increasing online guessing opportunity and backend authentication workload. This issue is fixed in version 0.62.6.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-307

Original publisher date fields

published: 2026-09-29T19:17:24.713

lastModified: 2026-09-30T20:17:24.100

Source published
29 Sep 2026 19:17:24 UTC
Source modified
30 Sep 2026 20:17:24 UTC
Saved here
25 Oct 2026 04:17:26 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

osv · GHSA-g6xm-f9xp-qq35

Published

### 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.

Source published
30 Sep 2026 23:26:17 UTC
Source modified
30 Sep 2026 23:30:05 UTC
Saved here
24 Oct 2026 13:19:54 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Publisher rating · LOW

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current