CVE-2025-9708: Kubernetes CSharp Client · Improper Certificate Validation
Affects Kubernetes CSharp ClientSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Kubernetes Kubernetes CSharp Client | Affected
| Fixed in– |
AI-suggested
1. Monitor for and apply official patches or updates from the Kubernetes project as soon as they become available to address this certificate validation flaw. 2. Until patches are released, implement strict network segmentation and firewall rules to restrict access to Kubernetes API servers and reduce exposure to potential man-in-the-middle attackers. 3. Use additional layers of authentication and authorization for Kubernetes API access, such as mutual TLS with properly validated certificates and role-based access control (RBAC). 4. Employ network monitoring and anomaly detection tools to identify suspicious TLS certificate usage or unexpected API server communications. 5. Consider deploying certificate pinning or custom validation logic in the C# client to enforce stricter trust chain verification. 6. Educate developers and DevOps teams about the risks of improper certificate validation and encourage secure coding and deployment practices. 7. Review and audit Kubernetes client usage across the organization to identify and remediate vulnerable instances of the C# client. 8. Engage with Kubernetes community and security advisories to stay informed about updates and best practices related to this vulnerability.
Description
A vulnerability exists in the Kubernetes C# client where the certificate validation logic accepts properly constructed certificates from any Certificate Authority (CA) without properly verifying the trust chain. This flaw allows a malicious actor to present a forged certificate and potentially intercept or manipulate communication with the Kubernetes API server, leading to possible man-in-the-middle attacks and API impersonation.