Event Monitor Cyber
EM-20261113-VBD9 VulnerabilityInfo severity

russh Vulnerability (CVE-2026-128088)

CVE-2026-128088

Share
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

  1. 1
    Born
    A second, independent source names it.
  2. 2
    Developing · Now
    New signals join; severity can move.
  3. 3
    Confirmed
    Not yet
    CISA KEV lists it, or exploitation in the wild is reported.
  4. 4
    Resolved
    Not yet
    Past the fix deadline and 14 days with no new signal.
  5. 5
    Archived
    Not yet
    30 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

  1. Disclosed: reached
    Nov 13 19:19 UTC
    C6 NVD published
  2. Scored: reached
    Nov 13 19:19 UTC
    CVSS 2.2
  3. Exploited: not yet
    Not yet
    No exploitation reported
  4. Advisories: not yet
    Not yet
    None yet
  5. Vendor Response: reached
    Nov 13 19:07 UTC
    C41 published
  6. Resolved: not yet
    Not yet
    After 14 quiet days

Timeline

14:0016:0018:0020:0022:00Nov 14BornC41 Red Hat Security DataC26 GitHub Advisory Database

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

Signals

  1. 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
  2. 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