EM-20261113-VBD9
VulnerabilityInfo severity
russh Vulnerability (CVE-2026-128088)
CVE-2026-128088
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 13 19:07 UTCC41 Red Hat Security Data
- Page Born
- Nov 13 19:10 UTCsecond source joined
- Last Signal
- Nov 13 19:10 UTC2 days before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 5 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 13 19:19 UTCC6 NVD published
- Scored: reachedNov 13 19:19 UTCCVSS 2.2
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 13 19:07 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-736f-c93q-9fwx / CVE-2026-128088: russh try_sign: asynchronous confirmation can sign after agent lock (opens source in a new tab) rust:russh Info severityDatabaseC26 GitHub Advisory Database
- Red Hat: CVE-2026-128088 (low) (opens source in a new tab) russh: russh: SSH agent lock bypass via unverified state during confirmation Info severityVendorC41 Red Hat Security Data