CVE-2026-56862

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-14. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

GO-2026-6090 - Go Packages

https://pkg.go.dev/vuln/GO-2026-6090
generic

crypto/tls: handshake messages can bypass non-advancing record limit in TLS 1.3 · Issue #80528 · golang/go · GitHub

https://go.dev/issue/80528

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgolang1-26-main-1.26.6-0.1.hum12026-08-14redhat
redhatgolang1-25-main-1.25.13-0.1.hum12026-08-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 43× 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-08-21 01:40 UTCEG score recompute
  2. 2026-08-21 01:40 UTCVendor advisory
  3. 2026-08-21 01:40 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 14:03 UTCVendor advisory
  6. 2026-08-20 14:03 UTCGHSA enrichment
  7. 2026-08-20 01:54 UTCEG score recompute
  8. 2026-08-20 01:54 UTCVendor advisory
  9. 2026-08-20 01:54 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 14:16 UTCVendor advisory
  12. 2026-08-19 14:16 UTCGHSA enrichment
  13. 2026-08-19 02:39 UTCVendor advisory
  14. 2026-08-19 02:39 UTCGHSA enrichment
  15. 2026-08-18 14:59 UTCEG score recompute
  16. 2026-08-18 14:59 UTCVendor advisory
  17. 2026-08-18 14:59 UTCGHSA enrichment
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-18 01:52 UTCVendor advisory
  20. 2026-08-18 01:51 UTCGHSA enrichment
  21. 2026-08-17 14:14 UTCEG score recompute
  22. 2026-08-17 14:14 UTCVendor advisory
  23. 2026-08-17 14:14 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 02:37 UTCVendor advisory
Show 18 more
  1. 2026-08-17 02:37 UTCGHSA enrichment
  2. 2026-08-16 15:00 UTCEG score recompute
  3. 2026-08-16 15:00 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 03:23 UTCEG score recompute
  6. 2026-08-16 03:23 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 15:46 UTCGHSA enrichment
  9. 2026-08-15 04:09 UTCEG score recompute
  10. 2026-08-15 04:09 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 16:32 UTCGHSA enrichment
  13. 2026-08-14 15:39 UTCEG score recompute 7.50
  14. 2026-08-14 15:39 UTCGHSA enrichment
  15. 2026-08-14 15:38 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  16. 2026-08-13 22:25 UTCNVD update
  17. 2026-08-13 22:09 UTCEG score recompute
  18. 2026-08-13 22:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56862?
CVE-2026-56862 is a high vulnerability published on August 13, 2026. Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
When was CVE-2026-56862 disclosed?
CVE-2026-56862 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56862 actively exploited?
CVE-2026-56862 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.2% of all scored CVEs.
What is the CVSS score of CVE-2026-56862?
CVE-2026-56862 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-56862?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56862, 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-56862

Explore →

Is Your Infrastructure Affected by CVE-2026-56862?

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