CVE-2026-102824

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.3 from GitHub Security Advisory (severity: MODERATE) published 2026-09-30. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-89207 (ENISA EUVD) · GHSA-w3jg-pjxf-73p4 (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Russh is a Rust SSH client and server library. Prior to 0.63.0, the hybrid ML-KEM 768 and X25519 implementation in russh/src/kex/hybrid_mlkem.rs accepts an all-zero 32-byte peer X25519 public key in both server_dh and compute_shared_secret, forcing the X25519 contribution to the combined shared secret to zero. A malicious SSH peer can therefore make the combined secret depend only on ML-KEM, defeating the hybrid exchange's intended fallback protection if ML-KEM is later weakened. This issue is fixed in version 0.63.0.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 29, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v0.63.0

Patch available: Eugeny/russh v0.63.0

https://github.com/Eugeny/russh/releases/tag/v0.63.0
GitHub commit Patch Available

commit 8da8967f1964 (Eugeny/russh)

Patch available: Eugeny/russh v0.63.0 (contains commit 8da8967f1964)

https://github.com/Eugeny/russh/commit/8da8967f196472576b1565d518a0ed60fce60f0c
GitHub advisoryMentions a patch (unverified)

Missing X25519 zero-point validation in hybrid ML-KEM key exchange · Advisory · Eugeny/russh · GitHub

https://github.com/Eugeny/russh/security/advisories/GHSA-w3jg-pjxf-73p4

Vendor Advisories for CVE-2026-102824(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshell-main-0.1.2-0.2.hum12026-10-01redhat
rustrussh @ 0.63.0 (fixes < 0.63.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
russh—
  • every version up to 0.63.0: fixed in 0.63.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-w3jg-pjxf-73p4 · GitHub severity MODERATE · GitHub CVSS 4.3
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-31 12:25 UTCOSV refresh
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-25 14:56 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-23 09:28 UTCEG score recompute
  16. 2026-10-23 09:28 UTCVendor advisory
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-18 05:10 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 44 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-12 16:40 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-11 22:32 UTCVendor advisory
  6. 2026-10-11 20:16 UTCEG score recompute
  7. 2026-10-11 18:28 UTCEG score recompute
  8. 2026-10-11 15:01 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-11 00:27 UTCEG score recompute
  11. 2026-10-11 00:27 UTCVendor advisory
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-10 02:19 UTCEG score recompute
  14. 2026-10-10 02:19 UTCVendor advisory
  15. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-09 04:15 UTCEG score recompute
  17. 2026-10-09 04:15 UTCVendor advisory
  18. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-08 06:11 UTCEG score recompute
  20. 2026-10-08 06:11 UTCVendor advisory
  21. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-07 08:07 UTCEG score recompute
  23. 2026-10-07 08:07 UTCVendor advisory
  24. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-06 10:03 UTCEG score recompute
  26. 2026-10-06 10:03 UTCVendor advisory
  27. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-10-05 11:54 UTCEG score recompute
  29. 2026-10-05 11:54 UTCVendor advisory
  30. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-10-04 13:50 UTCVendor advisory
  32. 2026-10-03 15:46 UTCEG score recompute
  33. 2026-10-03 15:46 UTCVendor advisory
  34. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-10-02 17:36 UTCEG score recompute
  36. 2026-10-02 17:36 UTCVendor advisory
  37. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-09-30 21:29 UTCEG score recompute
  39. 2026-09-30 20:27 UTCEG score recompute
  40. 2026-09-30 17:24 UTCEG score recompute
  41. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-09-29 19:20 UTCEG score recompute
  43. 2026-09-29 18:29 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  44. 2026-09-29 18:28 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-102824?
CVE-2026-102824 is a medium-severity vulnerability; its CVE record was published on September 29, 2026. Russh is a Rust SSH client and server library. Prior to 0.63.0, the hybrid ML-KEM 768 and X25519 implementation in russh/src/kex/hybrid_mlkem.rs accepts an all-zero 32-byte peer X25519 public key in both server_dh and compute_shared_secret, forcing the X25519 contribution to the combined shared…
When was the CVE record for CVE-2026-102824 published?
The CVE record for CVE-2026-102824 was published on September 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-102824 actively exploited?
CVE-2026-102824 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102824?
CVE-2026-102824 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102824?
A fix for CVE-2026-102824 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102824 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102824

Explore →

Is Your Infrastructure Affected by CVE-2026-102824?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs