CVE-2026-6412

MEDIUMNVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-06-25. NVD baseline CVSS 4.3; sources differ by 0.0.

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

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

Certificate policy and RFC 8446 compliance concerns regarding the continued acceptance of SHA-1/MD5 in certificate processing.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

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

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

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

Report cert verify failure with MD5

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

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

Vendor Advisories for CVE-2026-6412(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 5× in last 7d / 42× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 03:22 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-16 04:41 UTCGHSA enrichment
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:26 UTCGHSA enrichment
  10. 2026-07-14 00:07 UTCGHSA enrichment
  11. 2026-07-12 21:52 UTCGHSA enrichment
  12. 2026-07-11 19:37 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-10 17:22 UTCGHSA enrichment
  16. 2026-07-09 15:07 UTCGHSA enrichment
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 12:48 UTCGHSA enrichment
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-07 10:23 UTCGHSA enrichment
  23. 2026-07-06 08:06 UTCGHSA enrichment
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 17 more
  1. 2026-07-05 05:49 UTCGHSA enrichment
  2. 2026-07-04 03:27 UTCGHSA enrichment
  3. 2026-07-03 01:12 UTCGHSA enrichment
  4. 2026-07-01 22:57 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-06-30 20:42 UTCGHSA enrichment
  7. 2026-06-29 18:27 UTCEG score recompute▲ 2.00
  8. 2026-06-29 18:27 UTCGHSA enrichment
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-27 19:41 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 15:44 UTCEG score recompute▲ 2.30
  14. 2026-06-26 15:44 UTCGHSA enrichment
  15. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 2.3 · CVSS v4 → 2.3
  16. 2026-06-25 21:46 UTCEG score recompute
  17. 2026-06-25 21:46 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6412?
CVE-2026-6412 is a medium vulnerability published on June 25, 2026. Certificate policy and RFC 8446 compliance concerns regarding the continued acceptance of SHA-1/MD5 in certificate processing.
When was CVE-2026-6412 disclosed?
CVE-2026-6412 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-6412 actively exploited?
CVE-2026-6412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6412?
CVE-2026-6412 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-6412?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6412, 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-6412

Explore →

Is Your Infrastructure Affected by CVE-2026-6412?

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

Start Free Scan →Browse All CVEs