CVE-2026-10097

HIGHNVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
5.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_pr.
generic Patch Available

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/
github_pr

ML-KEM: fix AVX2 assembly

Fix merged in wolfSSL/wolfssl PR #10430 on 2026-05-12 — awaiting tagged release

https://github.com/wolfSSL/wolfssl/pull/10430

Vendor Advisories for CVE-2026-10097(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 38× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 03:56 UTCEG score recompute
  2. 2026-07-07 03:56 UTCGHSA enrichment
  3. 2026-07-06 16:29 UTCEG score recompute
  4. 2026-07-06 16:29 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 05:14 UTCEG score recompute
  7. 2026-07-06 05:13 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 17:57 UTCEG score recompute
  10. 2026-07-05 17:57 UTCGHSA enrichment
  11. 2026-07-05 06:41 UTCEG score recompute
  12. 2026-07-05 06:41 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 19:23 UTCEG score recompute
  16. 2026-07-04 19:23 UTCGHSA enrichment
  17. 2026-07-04 08:08 UTCEG score recompute
  18. 2026-07-04 08:08 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 20:49 UTCEG score recompute
  21. 2026-07-03 20:48 UTCGHSA enrichment
  22. 2026-07-03 09:33 UTCEG score recompute
  23. 2026-07-03 09:33 UTCGHSA enrichment
  24. 2026-07-02 22:17 UTCEG score recompute
  25. 2026-07-02 22:17 UTCGHSA enrichment
Show 36 more
  1. 2026-07-02 10:59 UTCEG score recompute
  2. 2026-07-02 10:59 UTCGHSA enrichment
  3. 2026-07-01 23:39 UTCEG score recompute
  4. 2026-07-01 23:39 UTCGHSA enrichment
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 12:22 UTCEG score recompute
  8. 2026-07-01 12:22 UTCGHSA enrichment
  9. 2026-07-01 01:06 UTCEG score recompute
  10. 2026-07-01 01:06 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 13:50 UTCEG score recompute
  13. 2026-06-30 13:50 UTCGHSA enrichment
  14. 2026-06-30 02:34 UTCEG score recompute
  15. 2026-06-30 02:34 UTCGHSA enrichment
  16. 2026-06-29 15:18 UTCEG score recompute
  17. 2026-06-29 15:18 UTCGHSA enrichment
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 04:00 UTCEG score recompute
  20. 2026-06-29 03:59 UTCGHSA enrichment
  21. 2026-06-28 16:38 UTCEG score recompute
  22. 2026-06-28 16:38 UTCGHSA enrichment
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 05:22 UTCEG score recompute
  25. 2026-06-28 05:22 UTCGHSA enrichment
  26. 2026-06-28 04:56 UTCEPSS rescore
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-27 18:06 UTCEG score recompute▲ 1.20
  29. 2026-06-27 18:06 UTCGHSA enrichment
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 7.5 · CVSS v4 → 8.3 · severity → HIGH
  32. 2026-06-26 15:45 UTCEG score recompute▲ 6.30
  33. 2026-06-26 15:45 UTCGHSA enrichment
  34. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 6.3 · CVSS v4 → 6.3
  35. 2026-06-25 21:46 UTCEG score recompute
  36. 2026-06-25 21:46 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10097?
CVE-2026-10097 is a high vulnerability published on June 25, 2026. wolfSSL's AVX2-optimized ML-KEM implementation (mlkemcmpavx2) 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…
When was CVE-2026-10097 disclosed?
CVE-2026-10097 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10097 actively exploited?
CVE-2026-10097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10097?
CVE-2026-10097 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10097, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10097

Explore →

Is Your Infrastructure Affected by CVE-2026-10097?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs