Improper Following of a Certificate's Chain of Trust Affecting github.com/juju/juju/internal/database package, versions >=3.2.0 <3.6.20>=4.0-beta1 <4.0.5
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Following of a Certificate's Chain of Trust vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMJUJUJUJUINTERNALDATABASE-16009305
- published13 Apr 2026
- disclosed2 Apr 2026
- creditHarry Pidcock
Introduced: 2 Apr 2026
CVE-2026-4370 Â (opens in a new tab)How to fix?
Upgrade github.com/juju/juju/internal/database to version 3.6.20, 4.0.5 or higher.
Overview
Affected versions of this package are vulnerable to Improper Following of a Certificate's Chain of Trust in the TLS Client/Server authentication for database cluster connections. An attacker can gain unauthorized access to the cluster, read and modify sensitive data, escalate privileges, and perform arbitrary actions by connecting to the cluster endpoint without proper certificate validation.
Workaround
This vulnerability can be mitigated by restricting access to the affected port (17666) using firewall rules to only allow trusted controller IP addresses, or by disabling high availability (HA) and blocking incoming and outgoing connections to port 17666. For Kubernetes controllers, apply a network policy to restrict access to the port.