PoC Monitor
← All CVEs
CVE-2026-10097published 25 Jun 2026 19:59 UTCData: JSON · API

wolfSSL

ML-KEM-1024 x64 AVX2 incomplete cipher text comparison enables IND-CCA2 break and static private-key recovery

wolfSSL's AVX2-optimized ML-KEM implementation (mlkem_cmp_avx2) compares only 1536 of the 1568 ciphertext bytes during the Fujisaki-Okamoto re-encryption check in ML-KEM-1024 decapsulation. Ciphertexts that differ from the expected re-encryption solely in bytes 1536-1567 bypass implicit rejection and are accepted as valid, breaking IND-CCA2 security. An attacker able to submit chosen ciphertexts to a decapsulation oracle that uses a static ML-KEM-1024 key, and to observe whether the genuine shared secret or the implicit-rejection secret was produced, can use this as a plaintext-checking oracle to recover the private key. A proof of concept recovered a full ML-KEM-1024 private key with approximately 98% success using roughly 350 chosen ciphertexts. The flaw is a deterministic logic error and does not rely on timing measurements.

First public PoC 27 daysafter publication · 22 Jul 2026
Public PoCs11 on GitHub
CVSS8.3high · scored by CNA · CWE-697
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

wolfSSL wolfSSL
  • >= 5.7.0, <= 5.9.1

Mitigation

The record names no fix. Check the vendor advisory below.

References

Timeline

Days relative to CVE publication
t=0+7+14+21+28CVE published25 Jun 2026 · t = 0First public PoC22 Jul 2026 · t+27d

First public PoC 27 days after publication; not in CISA KEV. First PoC: 007bsd/ml-kem-key-recovery (created 22 Jul 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
007bsd/ml-kem-key-recovery 22 Jul 2026 +27 d 0 PoC via PoC Index

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.