CVE-2026-6860

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-05-09. NVD baseline CVSS 5.3; sources differ by 0.0.

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

A fix is available — apply it.

A TCP client can perform a TLS handshake and present the server name extension with a server name that is accepted by a server wildcard name, e.g. if the server is configured with a certificate accepting *.example.com, any XYZ.example.com where xyz is a valid name can be used.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 12, 2026

Advisory Details (2)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

[Eclipse Vert.x] Possible DoS via unbounded server-side SNI SslContext cache growth (#381) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/381
generic

Define a bounded capacity for the internal SNI to SslContext cache. by vietj · Pull Request #6102 · eclipse-vertx/vert.x · GitHub

https://github.com/eclipse-vertx/vert.x/pull/6102

Vendor Advisories for CVE-2026-6860(11)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvertx-core2026-08-13redhat
redhatcryostat/jfr-datasource-rhel9:4.2.0-132026-07-29redhat
redhatrhbk/keycloak-rhel9-operator:26.6-82026-06-25redhat
redhatrhbk/keycloak-rhel9-operator:26.4-192026-06-25redhat
mavenio.vertx:vertx-core—ghsa

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.vertx:vertx-core5.0.0 ... 5.0.9 (12 versions)5.0.12—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 31× 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.

Showing the most recent 100 of 164 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6860?
CVE-2026-6860 is a medium vulnerability published on May 6, 2026. A TCP client can perform a TLS handshake and present the server name extension with a server name that is accepted by a server wildcard name, e.g. if the server is configured with a certificate accepting *.example.com, any XYZ.example.com where xyz is a valid name can be used.
When was CVE-2026-6860 disclosed?
CVE-2026-6860 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6860 actively exploited?
CVE-2026-6860 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 85.2% of all scored CVEs.
What is the CVSS score of CVE-2026-6860?
CVE-2026-6860 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-6860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6860, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6860

Explore →

Is Your Infrastructure Affected by CVE-2026-6860?

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

Start Free Scan →Browse All CVEs