Live › vulnerability › CVE-2026-116641
Go to dashboardDB Tools 100.19.0 was built with Go 1.26.8, which does not block certificates issued by the eMudhra certificate authorities, a list that Go 1.27.3 adds. The sources do not describe a concrete attack path beyond that gap in certificate trust checks.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 22:35 UTC. All times on this page are UTC.
Teams that run DB Tools 100.19.0 or earlier, which relies on the Go standard library TLS stack and the system CA store. The sources do not say whether exposure requires a specific connection path or configuration. Teams on later DB Tools builds can skip it.
No product ranges from the sources yet.
100.19.0 are listed as affected1.26.8 is listed as lacking the check100.20.0, which is built with Go 1.27.3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The DB Tools rely on the TLS implementation in Golang’s standard library, which generally uses the system CA store. However, the crypto/x509 package also has its own internal denylist of known-bad CA certificates. Golang 1.27.3 adds the eMudhra certificates to this list.
DB Tools version 100.19.0 was compiled with Golang 1.26.8, which does not include this check.
The issue is resolved by updating to Golang 1.27.3 in DB Tools 100.20.0
This page as .md · .json · in your agent: get_signal("CVE-2026-116641")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.