CVE-2026-6412

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100

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 (value × EchelonGraph’s weight)
Severity43% × 45%
The EG Score, 4.3 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

Auto-updated Jun 27, 2026
Fix referenced — no release confirmed yet. Sources: github_pr.
Web pageMentions a patch (unverified)

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/
GitHub pull request

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.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl4.6.0+p1-0+deb11u1 ... 5.9.2-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl5.5.4-2 ... 5.9.2-1 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl5.7.2-0.1 ... 5.9.2-1 (14 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 147 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-13 22:54 UTCOSV refresh
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-12 15:48 UTCEG score recompute
  6. 2026-10-11 19:33 UTCEG score recompute
  7. 2026-10-11 16:48 UTCEG score recompute
  8. 2026-10-11 14:09 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-23 08:29 UTCEG score recompute
  25. 2026-09-23 08:29 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
Show 73 more
  1. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-09-18 07:20 UTCEG score recompute
  5. 2026-09-18 07:20 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-09-14 01:17 UTCEG score recompute
  9. 2026-09-14 01:17 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  10. 2026-09-12 15:42 UTCEG score recompute
  11. 2026-09-12 15:42 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  12. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-08-30 19:30 UTCEG score recompute
  22. 2026-08-30 19:30 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-08-27 23:17 UTCEG score recompute
  27. 2026-08-27 23:17 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  28. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-08-24 21:50 UTCEG score recompute
  31. 2026-08-24 21:50 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  32. 2026-08-23 13:48 UTCEG score recompute
  33. 2026-08-23 13:48 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  34. 2026-08-23 00:19 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  35. 2026-08-22 11:33 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  36. 2026-08-21 09:18 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  37. 2026-08-20 07:01 UTCEG score recompute
  38. 2026-08-20 07:01 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  39. 2026-08-19 17:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-08-19 01:13 UTCEG score recompute
  41. 2026-08-19 01:13 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  42. 2026-08-18 13:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-08-16 16:01 UTCEG score recompute
  44. 2026-08-16 16:01 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  45. 2026-08-16 02:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  46. 2026-08-15 13:46 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  47. 2026-08-14 11:19 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  48. 2026-08-13 09:04 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  49. 2026-08-12 06:47 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  50. 2026-08-11 04:32 UTCEG score recompute
  51. 2026-08-11 04:32 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  52. 2026-08-11 00:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  53. 2026-08-10 02:17 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  54. 2026-08-09 00:03 UTCEG score recompute
  55. 2026-08-09 00:03 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  56. 2026-08-08 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  57. 2026-08-07 21:48 UTCEG score recompute
  58. 2026-08-07 21:48 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  59. 2026-08-06 19:33 UTCEG score recompute
  60. 2026-08-06 19:33 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  61. 2026-08-06 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  62. 2026-08-05 19:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  63. 2026-08-05 17:19 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  64. 2026-08-04 15:03 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  65. 2026-08-03 09:56 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  66. 2026-08-02 07:27 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  67. 2026-08-01 05:12 UTCEG score recompute
  68. 2026-08-01 05:12 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  69. 2026-08-01 04:16 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  70. 2026-07-31 02:57 UTCEG score recompute
  71. 2026-07-31 02:57 UTCGHSA enrichmentGHSA-w3gw-f9wr-g6qx · GitHub severity LOW · GitHub CVSS 4.3
  72. 2026-07-30 16:28 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  73. 2026-07-30 01:30 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-6412?
CVE-2026-6412 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-6412 published?
The CVE record for CVE-2026-6412 was published on June 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 27, 2026; the record at its source may have been updated since.
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% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-6412 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-6412 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs