CVE-2026-10097

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

Published Jun 25, 2026 CVSS 4.0 · 8.3 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability is an incomplete constant‑time ciphertext comparison in the AVX2 implementation of the Fujisaki‑Okamoto transform used by wolfSSL’s ML‑KEM‑1024. Because the final 32‑byte block of the 1568‑byte ciphertext is never compared, a ciphertext that is altered only in that block can be accepted, causing the library to return the true shared secret instead of performing the required implicit rejection. This flaw breaks IND‑CCA2 security and permits an attacker to obtain the session key. The issue aligns with CWE‑697: Incorrect Limit/Boundary Conditions.

Affected Systems

wolfSSL is the affected vendor and product. The CVE payload does not specify affected version ranges or precise build settings; the flaw is present in implementations that compile the AVX2 constant‑time comparison for the ML‑KEM‑1024 algorithm.

Risk and Exploitability

The CVSS score of 8.3 indicates high severity. The EPSS score of <1% indicates a very low but non‑zero probability of exploitation, and the vulnerability is not listed in CISA KEV, so the probability of widespread real‑world exploitation remains uncertain. However, the flaw can be leveraged by sending a manipulated ciphertext that differs only in the final 32 bytes during normal operation; if an attacker can influence the ciphertext sent to a vulnerable instance, they can recover the shared secret. No special privileges or additional conditions are described, so the attack path is purely data‑based.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update wolfSSL to the latest patch that addresses CVE‑2026‑10097.
  • If an wolfSSL without AVX2 support to eliminate the faulty constant‑time comparison.
  • Apply additional runtime checks for ciphertext validity, ensuring that implicit rejection is enforced even when AVX2 optimization is active.

Generated by OpenCVE AI on June 26, 2026 at 17:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description ML-KEM-1024 x64 AVX2 implicit rejection failure in the Fujisaki-Okamoto transform breaks IND-CCA2 security, allowing decapsulation to deviate from the implicit-rejection behavior required by the standard. The AVX2 constant-time ciphertext comparison used during decapsulation never compared the final 32-byte block of the 1568-byte ML-KEM-1024 ciphertext, so a ciphertext manipulated only in those final bytes would compare as equal and decapsulation returned the real shared secret instead of performing the required implicit rejection. 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.
Title ML-KEM-1024 x64 AVX2 implicit rejection failure breaks IND-CCA2 security ML-KEM-1024 x64 AVX2 incomplete cipher text comparison enables IND-CCA2 break and static private-key recovery
Weaknesses CWE-327 CWE-697
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

cvssV4_0

{'score': 8.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wolfssl
Wolfssl wolfssl
Vendors & Products Wolfssl
Wolfssl wolfssl
Type Values Removed Values Added
Description ML-KEM-1024 x64 AVX2 implicit rejection failure in the Fujisaki-Okamoto transform breaks IND-CCA2 security, allowing decapsulation to deviate from the implicit-rejection behavior required by the standard. The AVX2 constant-time ciphertext comparison used during decapsulation never compared the final 32-byte block of the 1568-byte ML-KEM-1024 ciphertext, so a ciphertext manipulated only in those final bytes would compare as equal and decapsulation returned the real shared secret instead of performing the required implicit rejection.
Title ML-KEM-1024 x64 AVX2 implicit rejection failure breaks IND-CCA2 security
Weaknesses CWE-327
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
wolfSSL
Published
Updated
Jun 26, 2026, 4:35 PM
Reserved
May 29, 2026, 3:01 PM
Status
Modified
Published
Jun 25, 2026, 8:17 PM
Modified
Jun 26, 2026, 5:16 PM