GHSA-253Q-9Q78-63X4

Vulnerability from github – Published: 2026-01-28 16:21 – Updated: 2026-01-28 16:21
VLAI?
Summary
Clatter has a PSK Validity Rule Violation issue
Details

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 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.

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

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "crates.io",
        "name": "clatter"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.2.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-24785"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-327"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-01-28T16:21:03Z",
    "nvd_published_at": "2026-01-28T00:15:50Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n\nProtocol 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.\n\nAffected 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.\n\n### Patches\n\nThe issue is fully patched and released in Clatter v2.2.0. The fixed version includes runtime checks to detect offending handshake patterns.\n\n### Workarounds\n\nAvoid using offending `*_psk0` variants of post-quantum patterns. Review custom handshake patterns carefully.\n\n### Resources\n\n* [PSK validity rule](https://noiseprotocol.org/noise.html#validity-rule)",
  "id": "GHSA-253q-9q78-63x4",
  "modified": "2026-01-28T16:21:03Z",
  "published": "2026-01-28T16:21:03Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/jmlepisto/clatter/security/advisories/GHSA-253q-9q78-63x4"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24785"
    },
    {
      "type": "WEB",
      "url": "https://github.com/jmlepisto/clatter/commit/b65ae6e9b8019bed5407771e21f89ddff17c5a71"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/jmlepisto/clatter"
    },
    {
      "type": "WEB",
      "url": "https://noiseprotocol.org/noise.html#validity-rule"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Clatter has a PSK Validity Rule Violation issue"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…