CVE-2026-105216 json
go-micro before 6.0.0 Disabled TLS Certificate Verification via tls.Config Helper
published 2026-10-04 35 d ago modified 2026-10-27 13 d ago also EUVD-2026-92119
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
go-micro before 6.0.0 contains an improper certificate validation vulnerability that allows network attackers to impersonate services because the shared TLS helper sets InsecureSkipVerify to true by default. Man-in-the-middle attackers can present any certificate to intercept or modify gRPC transport, HTTP and RabbitMQ broker, and Consul or etcd registry traffic, including authentication tokens and credentials.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 34 d ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- micro go-micro
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
github.com
/micro/go-micro/commit/c7657f73f45cf839e643db10f28703eeab7299c3
patch
-
github.com
/micro/go-micro/issues/2963
issue-tracking
-
github.com
/micro/go-micro/blob/v5.30.0/internal/util/tls/tls.go#L43-L67
technical-description
-
github.com
/micro/go-micro
product
-
vulncheck.com
/advisories/go-micro-before-6.0.0-disabled-tls-certificate-verification-via-tls-config-helper
third-party-advisory
Sources
- CVE List CVE-2026-105216
- NVD CVE-2026-105216
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.