CVE-2025-68121

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-02-05) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this week

Also known asEUVD-2025-206854 (ENISA EUVD) · GHSA-h355-32pf-p2xm (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

February 5, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
Patch available.
Web page

GO-2026-4337 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4337
Web page
https://groups.google.com/g/golang-announce/c/K09ubi9FQFk
Web page

crypto/tls: certificate chains aren't re-checked on resumption · Issue #77217 · golang/go · GitHub

https://go.dev/issue/77217
Web page
https://go.dev/cl/737700

Vendor Advisories for CVE-2025-68121(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhc-1:0.2.0-6.el8_4.22026-10-29redhat
redhatrhc-1:0.2.2-1.el8_8.32026-10-27redhat
redhatrhc-1:0.2.1-14.el8_6.12026-10-27redhat
redhatgo-toolset:rhel8-8040020261027035356.522a0ee42026-10-27redhat
redhatgrafana-0:7.5.15-12.el8_82026-10-22redhat
redhatgrafana-pcp-0:3.2.0-4.el8_6.22026-10-22redhat
redhatgrafana-pcp-0:3.2.0-6.el8_8.22026-10-22redhat
redhatlvms4/lvms-rhel8-operator:17925518852026-10-22redhat
redhatgrafana-0:7.5.11-12.el8_62026-10-22redhat
redhatgo-toolset:rhel8-8080020261020152326.6b4b45d82026-10-21redhat
redhatgo-toolset:rhel8-8060020261020153812.97d7f71f2026-10-21redhat
redhatcert-manager/cert-manager-operator-rhel9:17890290762026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17914597112026-10-13redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17914597592026-10-13redhat
redhatcompliance/openshift-selinuxd-rhel8:17906228982026-10-06redhat
redhatgit-lfs-0:2.13.3-3.el8_6.82026-09-28redhat
redhatgit-lfs-0:3.4.1-4.el9_4.62026-09-28redhat
redhatgit-lfs-0:3.2.0-2.el8_8.82026-09-28redhat
redhatosbuild-composer-0:46.3-8.el8_62026-09-21redhat
redhatopenshift4/ose-ansible-operator:17888450832026-09-17redhat
redhatopenshift4/ose-sdn-rhel8:17888462862026-09-17redhat
redhatosbuild-composer-0:75-10.el8_82026-09-17redhat
redhatopenshift-clients-0:4.13.0-202608122150.p2.gd192e90.assembly.stream.el82026-09-17redhat
redhatgit-lfs-0:3.2.0-2.el9_2.102026-09-14redhat
redhattripleo-ansible-0:3.3.1-17.1.20260603190918.8debef3.el9ost2026-09-10redhat
redhatopenshift-clients-0:4.17.0-202608201812.p2.g7189593.assembly.stream.el82026-09-03redhat
redhatopenshift4/ovirt-csi-driver-rhel8-operator:17867529822026-09-03redhat
redhatopenshift4/ose-ansible-operator:17867522962026-09-03redhat
redhatopenshift-clients-0:4.12.0-202608131627.p2.gd691257.assembly.stream.el82026-09-03redhat
redhatopenshift-clients-0:4.14.0-202608131802.p2.g44b3ac2.assembly.stream.el82026-08-26redhat

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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.251.25.0-1, 1.25.0-2, 1.25.1-1, 1.25.2-1, 1.25.3-1
  • every version up to 1.25.6-1: fixed in 1.25.6-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
stdlib—
  • every version up to 1.24.13: fixed in 1.24.13
  • 1.25.0-0 up to 1.25.7: fixed in 1.25.7
  • 1.26.0-rc.1 up to 1.26.0-rc.3: fixed in 1.26.0-rc.3
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 28× in last 7d / 97× 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 99 of 326 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 227 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-68121?
CVE-2025-68121 is a critical-severity vulnerability; its CVE record was published on February 5, 2026. During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the…
When was the CVE record for CVE-2025-68121 published?
The CVE record for CVE-2025-68121 was published on February 5, 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 17, 2026; the record at its source may have been updated since.
Is CVE-2025-68121 actively exploited?
CVE-2025-68121 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68121?
CVE-2025-68121 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2025-68121?
A fix for CVE-2025-68121 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68121 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-2025-68121

Explore →

Is Your Infrastructure Affected by CVE-2025-68121?

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

Book a Demo →Browse All CVEs