Security readout for executives and security teams
Plain-English summary
CVE-2026-24785 affects Clatter, a Rust Noise protocol library. Versions before 2.2.0 allowed certain post-quantum pre-shared-key handshake patterns that break Noise’s PSK validity rule. This can weaken encryption guarantees and may risk catastrophic key reuse in affected designs. The vendor reports the issue is fixed in Clatter 2.2.0.
Executive priority
Prioritize remediation where Clatter protects sensitive or long-lived communications, especially in products using post-quantum PSK handshakes. Treat as high priority for affected deployments because cryptographic design failures can undermine confidentiality and integrity without obvious operational symptoms.
Technical view
Clatter before 2.2.0 permitted PQ and hybrid `*_psk0` handshake patterns that violated Noise Framework Section 9.3. PSK-derived keys could be used for encryption without proper randomization from self-chosen ephemeral randomness. Affected defaults include `noise_pqkk_psk0`, `noise_pqkn_psk0`, `noise_pqnk_psk0`, and `noise_pqnn_psk0`. CWE-327 applies.
Likely exposure
Exposure is limited to applications or embedded systems using the jmlepisto Clatter Rust crate before 2.2.0, especially with the named post-quantum `*_psk0` patterns or similar custom hybrid patterns. Systems not using Clatter, not using affected PSK0 PQ patterns, or already on 2.2.0 are not indicated as affected by the provided sources.
Exploitation context
No source provided states active exploitation, and the CVE is not marked KEV. This is a cryptographic protocol compliance flaw, not a typical remote code execution issue. Business impact depends on whether affected handshakes protect sensitive communications and whether keys or sessions could be reused under weakened guarantees.
Researcher notes
The strongest evidence is the GitHub advisory and referenced patch. The issue centers on Noise Section 9.3 PSK validity, with Clatter 2.2.0 adding runtime detection for offending patterns. Public evidence in the bundle does not show exploitation, affected downstream products, or practical attack demonstrations.
Mitigation direction
- Upgrade Clatter to version 2.2.0 or later.
- Avoid offending post-quantum `*_psk0` handshake variants.
- Review custom handshake patterns against the Noise PSK validity rule.
- Follow the GitHub advisory for any additional vendor guidance.
Validation and detection
- Inventory Rust projects and firmware for Clatter dependency versions.
- Identify use of `noise_pqkk_psk0`, `noise_pqkn_psk0`, `noise_pqnk_psk0`, or `noise_pqnn_psk0`.
- Review custom PQ or hybrid PSK patterns for validity-rule compliance.
- Confirm Clatter 2.2.0 runtime checks are present after upgrade.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-24785 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jmlepisto/clatter/security/advisories/GHSA-253q-9q78-63x4CVE reference · x_refsource_CONFIRM
- https://github.com/jmlepisto/clatter/commit/b65ae6e9b8019bed5407771e21f89ddff17c5a71CVE reference · x_refsource_MISC
- https://noiseprotocol.org/noise.html#validity-ruleCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.