RUSTSEC-2026-0331None▾ SunlitPanic on Decoding Short Hybrid Keys
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
The deserialization functions X25519MlKem768Draft00PrivateKey::decode X25519MlKem768Draft00PublicKey::decode and XWingKemDraft06PublicKey::decode would panic during an indexing operation when provided an input slice that is shorter than the length of the given key type, i.e. shorter than 2400 bytes in the case of the X25519MlKem768Draft00 private key and shorter than 1184 bytes in the case of the X25519MlKem768Draft and XWingKemDraft06 public keys.
Applications decoding attacker provided slices into the above mentioned private and public key types could be made to panic.
With release of version 0.0.10 of libcrux-kem this bug has been fixed and the serialization functions return InvalidPrivateKey and InvalidPublicKey errors on invalid input buffer lengths.
We recommend users upgrade to libcrux-kem version 0.0.10.
libcrux-kem >= 0.0.0-0, < 0.0.10Upgrade to a patched release:
libcrux-kem 0.0.10Connected by shared product, vendor, weakness, or advisory.