CVE-2026-10512

HIGHNVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: LOW) 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.

The X25519 x86_64 assembly implementation fails to clear the most significant bit during the final modular reduction, so the computed result may not be fully reduced modulo the field prime 2^255 - 19. This can leave the field element in a non-canonical form, producing an incorrect result from the scalar multiplication and potentially a wrong shared secret. The final carry-propagation chains in the x64 and AVX2 reduction routines could overflow into the top bit, and the high limb was not masked afterward, so the 255-bit field element was left non-canonical.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
17.7%
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

X25519 x64 ASM: fix full reduction

Fix merged in wolfSSL/wolfssl PR #10536 on 2026-06-03 — awaiting tagged release

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

Vendor Advisories for CVE-2026-10512(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 36× in last 7d / 49× 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-06 18:54 UTCEG score recompute
  2. 2026-07-06 18:54 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 06:43 UTCEG score recompute
  5. 2026-07-06 06:43 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 18:34 UTCEG score recompute
  8. 2026-07-05 18:34 UTCGHSA enrichment
  9. 2026-07-05 06:24 UTCEG score recompute
  10. 2026-07-05 06:24 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 18:11 UTCEG score recompute
  14. 2026-07-04 18:10 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 05:52 UTCEG score recompute
  17. 2026-07-04 05:51 UTCGHSA enrichment
  18. 2026-07-03 17:39 UTCEG score recompute
  19. 2026-07-03 17:39 UTCGHSA enrichment
  20. 2026-07-03 05:29 UTCEG score recompute
  21. 2026-07-03 05:29 UTCGHSA enrichment
  22. 2026-07-02 17:11 UTCEG score recompute
  23. 2026-07-02 17:11 UTCGHSA enrichment
  24. 2026-07-02 04:55 UTCEG score recompute
  25. 2026-07-02 04:55 UTCGHSA enrichment
Show 24 more
  1. 2026-07-01 16:46 UTCEG score recompute
  2. 2026-07-01 16:46 UTCGHSA enrichment
  3. 2026-07-01 15:06 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 04:37 UTCEG score recompute
  6. 2026-07-01 04:37 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 16:26 UTCEG score recompute
  9. 2026-06-30 16:26 UTCGHSA enrichment
  10. 2026-06-30 04:17 UTCEG score recompute
  11. 2026-06-30 04:17 UTCGHSA enrichment
  12. 2026-06-29 16:06 UTCEG score recompute 5.20
  13. 2026-06-29 16:06 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-06-26 15:45 UTCEG score recompute 2.30
  21. 2026-06-26 15:45 UTCGHSA enrichment
  22. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 2.3 · CVSS v4 → 2.3
  23. 2026-06-25 21:46 UTCEG score recompute
  24. 2026-06-25 21:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-10512?
CVE-2026-10512 is a high vulnerability published on June 25, 2026. The X25519 x86_64 assembly implementation fails to clear the most significant bit during the final modular reduction, so the computed result may not be fully reduced modulo the field prime 2^255 - 19. This can leave the field element in a non-canonical form, producing an incorrect result from the…
When was CVE-2026-10512 disclosed?
CVE-2026-10512 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-10512 actively exploited?
CVE-2026-10512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10512?
CVE-2026-10512 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10512, 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-10512

Explore →

Is Your Infrastructure Affected by CVE-2026-10512?

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