CVE-2026-6860: Eclipse Vert.x · CWE-295
Affects Eclipse Vert.xSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse Vert.x | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, users should be aware of this validation weakness and consider additional TLS validation controls or network-level mitigations if possible. Monitor vendor communications for updates on patches or official mitigations.
Description
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.