How many CVEs have patched auth_attempts_capped_at_max?

1 published CVEs changed auth_attempts_capped_at_max in Eugeny/russh, in 1 distinct patches totalling 74 changed lines, between 2026 and 2026.

What is the latest CVE that changed auth_attempts_capped_at_max?

CVE-2026-102825 (Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path), published 2026-09-29, changed lines 184 to 257 of russh/src/server/encrypted.rs.

How does auth_attempts_capped_at_max compare to the rest of Eugeny/russh?

Eugeny/russh has 13 CVEs with a located fix in total; 1 of them changed auth_attempts_capped_at_max.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

Eugeny/russh

Function

auth_attempts_capped_at_max

Name: auth_attempts_capped_at_max in Eugeny/russh: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

russh/src/server/encrypted.rs

Last patched September 29, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

74

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

auth_attempts_capped_at_max in Eugeny/russh was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 74 lines in total.

Eugeny/russh has 13 CVEs with a located fix in total, so 8% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed auth_attempts_capped_at_max, newest first, with the lines each fix touched.

Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path
CVE-2026-102825 · lines 184–257 · +74 −0
Low · CVSS 3.7
EPSS 0.3%2026-09-29

Get an alert when the next CVE fix lands in Eugeny/russh, with the patched functions.

Monitor russh CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in Eugeny/russh changed by the most CVE fixes.

is_established_channel2 CVEs · russh/src/server/encrypted.rs encode_mpint_all_zero_is_empty_mpint2 CVEs · russh/src/kex/mod.rs compute_shared_secret2 CVEs · russh/src/kex/curve25519.rs process_packet1 CVEs · russh/src/server/encrypted.rs server_handle_channel_open1 CVEs · russh/src/server/encrypted.rs kex_ecdh_init1 CVEs · russh/src/kex/curve25519.rs

All patched functions in Eugeny/russh

Frequently asked questions

Common questions about CVE fixes to auth_attempts_capped_at_max.

How many CVEs have patched auth_attempts_capped_at_max?: 1 published CVEs changed auth_attempts_capped_at_max in Eugeny/russh, in 1 distinct patches totalling 74 changed lines, between 2026 and 2026.
What is the latest CVE that changed auth_attempts_capped_at_max?: CVE-2026-102825 (Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path), published 2026-09-29, changed lines 184 to 257 of russh/src/server/encrypted.rs.
How does auth_attempts_capped_at_max compare to the rest of Eugeny/russh?: Eugeny/russh has 13 CVEs with a located fix in total; 1 of them changed auth_attempts_capped_at_max.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track Eugeny/russh CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing