Bug-Fixes in libcrux-ecdh, libcrux-ed25519, libcrux-psq

Exploitation

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

CVSS 4.0

0.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

In accordance with our security policy for libcrux, we publish a GitHub security advisory for any releases whose CHANGELOG includes bug-fixes, and encourage our users to upgrade. The latest releases of the libcrux-ecdh, libcrux-ed25519 and libcrux-psq crates contain the following bug-fixes: libcrux-ecdh - #1301: Check length and clamping in X25519 secret validation. This is a breaking change since errors are now raised on unclamped X25519 secrets or inputs of the wrong length libcrux-ed25519 - #1320: Remove duplicated clamping step during key generation The issue fixed in #1320 was first reported by Nadim Kobeissi. libcrux-psq - #1319: Propagate AEADError instead of panicking - #1301: Fix broken clamping check for imported X25519 secret keys The issue fixed in #1319 was first reported by Nadim Kobeissi.

Published by the source

12 Feb 2026, 22:12 UTC

Last modified by the source

27 Feb 2026, 20:51 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-435g-fcv3-8j26

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

# Patch Next advisory brief: GHSA-435g-fcv3-8j26

Advisory: Bug-Fixes in `libcrux-ecdh`, `libcrux-ed25519`, `libcrux-psq`
IDs: GHSA-435g-fcv3-8j26
Record: https://patchnext.com/advisories/ghsa-435g-fcv3-8j26 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated (CVSS 0.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: libcrux-ed25519 0.0.6; libcrux-ecdh 0.0.6; libcrux-psq 0.0.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io libcrux-ed25519: affected <= 0.0.5; fixed in 0.0.6
- crates.io libcrux-ecdh: affected <= 0.0.5; fixed in 0.0.6
- crates.io libcrux-psq: affected <= 0.0.6; fixed in 0.0.7

## Suggested inspection (read-only)
- crates.io libcrux-ed25519: check the installed version with your package manager.
- crates.io libcrux-ecdh: check the installed version with your package manager.
- crates.io libcrux-psq: 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 libcrux-ed25519, libcrux-ecdh, libcrux-psq.
- 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-435g-fcv3-8j26 (GitHub-reviewed advisory GHSA-435g-fcv3-8j26 lists affected ranges: crates.io libcrux-ecdh >=0 =0 =0 <=0.0.6)

Commands are suggestions: review each one before running it.