Clatter has a PSK Validity Rule Violation issue

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.0 · 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 · score source

EPSS

• CVE-2026-24785: 0.14% estimated exploitation activity in the next 30 days; percentile 3.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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 noisepqkkpsk0, noisepqknpsk0, noisepqnkpsk0, noisepqnnpsk0, and some hybrid variants. Users of these patterns may have been using handshakes that do not meet the intended security properties. Patches The issue is fully patched and released in Clatter v2.2.0. The fixed version includes runtime checks to detect offending handshake patterns. Workarounds Avoid using offending psk0 variants of post-quantum patterns. Review custom handshake patterns carefully. Resources PSK validity rule

Published by the source

28 Jan 2026, 16:21 UTC

Last modified by the source

28 Jan 2026, 16:21 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-253q-9q78-63x4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24785

Advisory: Clatter has a PSK Validity Rule Violation issue
IDs: CVE-2026-24785, GHSA-253q-9q78-63x4
Record: https://patchnext.com/advisories/cve-2026-24785 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: clatter 2.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io clatter: affected < 2.2.0; fixed in 2.2.0

## Suggested inspection (read-only)
- crates.io clatter: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on clatter.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-253q-9q78-63x4 (GitHub-reviewed advisory GHSA-253q-9q78-63x4 lists affected ranges: crates.io clatter >=0 <2.2.0)

Commands are suggestions: review each one before running it.