Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-j7h2-66j4-ghjf

A russh SSH server accepts a publickey authentication whose signature uses a different algorithm than the one named in the request

CVSS 2.3 Low

Published by the GitHub Advisory Database at 19 Oct 2026, 17:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
russhcrates.io>=0.34.0-beta.1, <0.64.00.64.0
Identifiers
GHSA-j7h2-66j4-ghjf · CVE-2026-111062
Weakness (CWE)
CWE-347
Tags
Published
19 Oct 2026
Updated
19 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

russh versions from 0.34.0-beta.1 before 0.64.0 do not check that a publickey signature's algorithm matches the one named in the authentication request. A client holding a valid RSA key can get a SHA-1 signature accepted by a server that is set to refuse SHA-1. Upgrade to russh 0.64.0.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.3 Low 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV
  3. 5 Nov 2026, 20:47 UTC Confirmed by the CVE List
  4. 5 Nov 2026, 21:18 UTC Confirmed by NVD

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.