Description
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.
Published: 2026-01-27
Score: 8 High
EPSS: < 1% Very Low
KEV: No
Impact: Key misuse due to PSK validity rule violation
Action: Apply Patch
AI Analysis

Impact

Clatter, a Rust implementation of the Noise protocol, contains a protocol compliance flaw in versions before 2.2.0. The library accepted post‑quantum handshake patterns that violate the PSK validity rule, allowing PSK‑derived keys to be combined with self‑chosen nonce values without proper randomization. This undermines the integrity of encryption and can enable catastrophic key reuse, effectively erasing the confidentiality guarantees of the protocol.

Affected Systems

The vulnerability affects the "jmlepisto:clatter" library in all releases older than 2.2.0. Default post‑quantum handshake patterns, such as noise_pqkk_psk0, noise_pqkn_psk0, noise_pqnk_psk0, noise_pqnn_psk0 and several hybrid variants, are impacted. Users incorporating these patterns in their applications are exposed.

Risk and Exploitability

The CVSS score of 8 indicates a high severity, while the EPSS score of less than 1 % suggests a low likelihood of exploitation in the wild. The flaw is not listed in the CISA KEV catalog. Exploitation requires an application to use the vulnerable library in a handshake that contains a *psk0* pattern; an attacker who can influence the handshake parameter selection could obtain a weak key and conduct cryptographic attacks. The likely attack vector is through libraries used in server or client software that opts for post‑quantum Noise patterns without verifying the PSK validity rule.

Generated by OpenCVE AI on April 18, 2026 at 01:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Clatter to version 2.2.0 or newer to receive the official fix.
  • Avoid using any *_psk0 post‑quantum handshake patterns until the library is updated, and review any custom handshake definitions to ensure they comply with the PSK validity rule.
  • If an upgrade cannot be performed immediately, restrict the application to use only non‑PSK or strictly validated handshake patterns and monitor for any anomalies related to key reuse.

Generated by OpenCVE AI on April 18, 2026 at 01:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-253q-9q78-63x4 Clatter has a PSK Validity Rule Violation issue
History

Fri, 27 Feb 2026 21:45:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:jmlepisto:clatter:*:*:*:*:*:rust:*:*
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Wed, 28 Jan 2026 15:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 28 Jan 2026 12:30:00 +0000

Type Values Removed Values Added
First Time appeared Jmlepisto
Jmlepisto clatter
Vendors & Products Jmlepisto
Jmlepisto clatter

Tue, 27 Jan 2026 23:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Clatter has a PSK Validity Rule Violation issue
Weaknesses CWE-327
References
Metrics cvssV4_0

{'score': 8, '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'}


Subscriptions

Jmlepisto Clatter
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-01-28T15:10:48.864Z

Reserved: 2026-01-26T21:06:47.870Z

Link: CVE-2026-24785

cve-icon Vulnrichment

Updated: 2026-01-28T15:10:41.793Z

cve-icon NVD

Status : Analyzed

Published: 2026-01-28T00:15:50.623

Modified: 2026-02-27T21:39:21.017

Link: CVE-2026-24785

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-18T02:00:10Z

Weaknesses