Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-w3jg-pjxf-73p4

Russh: Missing X25519 zero-point validation in hybrid ML-KEM key exchange

CVSS 4.3 MediumEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 30 Sept 2026, 23:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
russhcrates.io<0.63.00.63.0
Identifiers
GHSA-w3jg-pjxf-73p4 · CVE-2026-102824
Weakness (CWE)
CWE-327
Tags
Published
30 Sept 2026
Updated
30 Sept 2026

Machine-written summary

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

The russh package, versions before 0.63.0, does not check that the X25519 public key sent by the remote peer in the hybrid ML-KEM 768 plus X25519 key exchange is the all-zero point. An attacker able to intercept or send key exchange messages can force the X25519 contribution to the shared secret to zero, leaving the exchange protected only by ML-KEM 768. Upgrade to russh 0.63.0 or later. The source gives no workaround.

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
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

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.