CVE-2026-6330

MEDIUMNVD 6.56.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

The ML-KEM ARM64 NEON ciphertext comparison only compares half of the input, breaking the Fujisaki-Okamoto transform's implicit rejection and weakening IND-CCA2 security on that code path. The constant-time comparison effectively ignored part of the re-encrypted ciphertext, so a decapsulating party could fail to detect a manipulated ciphertext and proceed without the standard's required implicit rejection.

CVSS v3
6.5
EG Score
6.5(high)
EPSS
3.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

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

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

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

Various fixes

Fix merged in wolfSSL/wolfssl PR #10192 on 2026-04-15 — awaiting tagged release

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

Vendor Advisories for CVE-2026-6330(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 22× in last 7d / 37× 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 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 07:54 UTCEG score recompute
  4. 2026-07-06 07:53 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 09:15 UTCEG score recompute
  8. 2026-07-05 09:15 UTCGHSA enrichment
  9. 2026-07-04 10:45 UTCEG score recompute
  10. 2026-07-04 10:45 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-03 12:10 UTCEG score recompute
  14. 2026-07-03 12:10 UTCGHSA enrichment
  15. 2026-07-02 13:17 UTCEG score recompute
  16. 2026-07-02 13:16 UTCGHSA enrichment
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 14:47 UTCEG score recompute
  19. 2026-07-01 14:47 UTCGHSA enrichment
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 16:17 UTCEG score recompute
  22. 2026-06-30 16:17 UTCGHSA enrichment
  23. 2026-06-29 17:48 UTCEG score recompute
  24. 2026-06-29 17:47 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 12 more
  1. 2026-06-28 19:18 UTCEG score recompute▲ 0.20
  2. 2026-06-28 19:18 UTCGHSA enrichment
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 21:42 UTCNVD updateCVSS v3 → 6.5
  6. 2026-06-27 20:49 UTCEG score recompute
  7. 2026-06-27 20:49 UTCGHSA enrichment
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 22:19 UTCEG score recompute
  10. 2026-06-26 22:19 UTCGHSA enrichment
  11. 2026-06-25 23:51 UTCEG score recompute
  12. 2026-06-25 23:50 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6330?
CVE-2026-6330 is a medium vulnerability published on June 25, 2026. The ML-KEM ARM64 NEON ciphertext comparison only compares half of the input, breaking the Fujisaki-Okamoto transform's implicit rejection and weakening IND-CCA2 security on that code path. The constant-time comparison effectively ignored part of the re-encrypted ciphertext, so a decapsulating party…
When was CVE-2026-6330 disclosed?
CVE-2026-6330 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6330 actively exploited?
CVE-2026-6330 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6330?
CVE-2026-6330 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-6330?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6330, 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-6330

Explore →

Is Your Infrastructure Affected by CVE-2026-6330?

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

Start Free Scan →Browse All CVEs