CVE-2026-24785

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-4896 (ENISA EUVD) · GHSA-253q-9q78-63x4 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Clatter is a no_std compatible, pure Rust implementation of the Noise protocol framework with post-quantum support. Versiosn prior to2.2.0 have a protocol compliance vulnerability. The library allowed post-quantum handshake patterns that violated the PSK validity rule (Noise Protocol Framework Section 9.3). This could allow PSK-derived keys to be used for encryption without proper randomization by self-chosen ephemeral randomness, weakening security guarantees and potentially allowing catastrophic key reuse. Affected default patterns include noise_pqkk_psk0, noise_pqkn_psk0, noise_pqnk_psk0, noise_pqnn_psk0, and some hybrid variants. Users of these patterns may have been using handshakes that do not meet the intended security properties. The issue is fully patched and released in Clatter v2.2.0. The fixed version includes runtime checks to detect offending handshake patterns. As a workaround, avoid using offending *_psk0` variants of post-quantum patterns. Review custom handshake patterns carefully.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

January 28, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
Web page

The Noise Protocol Framework

https://noiseprotocol.org/noise.html#validity-rule
GitHub advisoryMentions a patch (unverified)

PSK Validity Rule Violation · Advisory · jmlepisto/clatter · GitHub

https://github.com/jmlepisto/clatter/security/advisories/GHSA-253q-9q78-63x4
GitHub commit Patch Available

commit b65ae6e9b801 (jmlepisto/clatter)

Patch available: jmlepisto/clatter clatter-v2.2.0 (contains commit b65ae6e9b801)

https://github.com/jmlepisto/clatter/commit/b65ae6e9b8019bed5407771e21f89ddff17c5a71

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustclatter @ 2.2.0 (fixes < 2.2.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
clatter—
  • every version up to 2.2.0: fixed in 2.2.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 56× 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.

Showing the most recent 99 of 215 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-01 14:13 UTCGHSA enrichmentGHSA-253q-9q78-63x4 · GitHub severity HIGH
  3. 2026-11-01 07:57 UTCGHSA enrichmentGHSA-253q-9q78-63x4 · GitHub severity HIGH
  4. 2026-11-01 07:57 UTCEG score recompute
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-31 12:32 UTCEG score recompute
  7. 2026-10-30 10:51 UTCEG score recompute
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-29 09:09 UTCEG score recompute
  10. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-28 07:29 UTCEG score recompute
  12. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-27 05:48 UTCEG score recompute
  14. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-26 00:04 UTCEG score recompute
  16. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-25 14:40 UTCEG score recompute
  18. 2026-10-24 22:23 UTCEG score recompute
  19. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-23 20:42 UTCEG score recompute
  21. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-22 19:01 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-21 17:19 UTCEG score recompute
  25. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 74 more
  1. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-20 15:24 UTCEG score recompute
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-19 13:40 UTCEG score recompute
  5. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-18 03:53 UTCEG score recompute
  7. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-17 10:17 UTCEG score recompute
  9. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-16 08:35 UTCEG score recompute
  11. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-15 06:52 UTCEG score recompute
  13. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-14 02:36 UTCEG score recompute
  15. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-12 22:48 UTCEG score recompute
  17. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-12 16:19 UTCEG score recompute
  19. 2026-10-11 20:02 UTCEG score recompute
  20. 2026-10-11 17:15 UTCEG score recompute
  21. 2026-10-11 14:46 UTCEG score recompute
  22. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-09 09:58 UTCOSV refresh
  26. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-09-19 17:03 UTCOSV refresh
  42. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-08-31 20:34 UTCOSV refresh
  56. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  62. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  63. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  64. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  66. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  67. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  68. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  69. 2026-08-14 12:08 UTCEG score recompute
  70. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  71. 2026-08-13 04:12 UTCEG score recompute
  72. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  73. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  74. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24785?
CVE-2026-24785 is a critical-severity vulnerability; its CVE record was published on January 28, 2026. Clatter is a no_std compatible, pure Rust implementation of the Noise protocol framework with post-quantum support. Versiosn prior to2.2.0 have a protocol compliance vulnerability. The library allowed post-quantum handshake patterns that violated the PSK validity rule (Noise Protocol Framework…
When was the CVE record for CVE-2026-24785 published?
The CVE record for CVE-2026-24785 was published on January 28, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-24785 actively exploited?
CVE-2026-24785 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-24785?
CVE-2026-24785 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-24785?
A fix for CVE-2026-24785 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-24785?

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

Book a Demo →Browse All CVEs