Skip to content
major vulnerability· requires attention

Crypto flaw in widely-used wolfSSL ML-KEM-1024 allows private-key recovery via chosen ciphertexts, impacting TLS/embedded systems.

Cryptography

CVE-2026-10097

8.3
High
EPSS 0.26%Patch availableJun 27, 2026

IND-CCA2 flaw in wolfSSL ML-KEM-1024 decapsulation; private key recovery.

common questions

Is CVE-2026-10097 being exploited?

Not confirmed. CVE-2026-10097 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-10097?

CVE-2026-10097 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-10097?

Yes. A fix has been recorded for CVE-2026-10097. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-10097 affect?

CVE-2026-10097 affects wolfSSL ML-KEM-1024, TLS deployments using wolfSSL, Embedded systems using ML-KEM-1024. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-10097?

Plan upgrade to patched wolfSSL ML-KEM; monitor advisories.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
wolfSSL ML-KEM-1024TLS deployments using wolfSSLEmbedded systems using ML-KEM-1024
impact

Attackers can recover ML-KEM-1024 private key via chosen ciphertexts, enabling decryption and impersonation.

action required

Monitor only

affected versions
wolfSSL wolfSSL
  • affected>= 5.7.0 and <= 5.9.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free