8

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-24785

CVE-2026-24785: Clatter has a PSK Validity Rule Violation issue

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-24785

CVE-2026-24785:

8

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
clatter	rust	< 2.2.0	2.2.0

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a protocol compliance issue in the clatter library, where certain handshake patterns involving pre-shared keys (PSKs) violated the PSK validity rule from the Noise Protocol Framework. This could allow an attacker to weaken the security guarantees of the handshake, potentially leading to key reuse.

The analysis of the patch commit b65ae6e9b8019bed5407771e21f89ddff17c5a71 shows the vulnerability had two root causes:

Lack of Pattern Validation: The HandshakePattern::new constructor and the HandshakePattern::add_psks helper function did not validate that the created handshake patterns adhered to the PSK validity rule. This allowed insecure patterns to be created. The patch addresses this by introducing validation logic in a new try_new function that is used by both new and add_psks.
Missing Runtime Enforcement: The write_message methods in NqHandshakeCore, PqHandshakeCore, and HybridHandshakeCore would process these invalid patterns without any checks. This is where the vulnerability would manifest at runtime, as these functions would proceed to use PSK-derived keys for encryption without the required randomization from a self-chosen ephemeral key. The patch adds runtime checks to these functions to detect and prevent this insecure state, returning a PskValidityViolation error.

Additionally, the library itself provided several vulnerable patterns (e.g., noise_pqkk_psk0, noise_hybrid_nk_psk0), which were removed in the patch. An exploit would involve an application using one of these vulnerable patterns (or a custom-defined one) and then calling the write_message function, which would appear in a runtime profile or stack trace.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.