The eMudhra Certificate Authority Compromise: What It Means for TeamCity - The JetBrains Blog
Blog post from JetBrains
In October 2026, eight eMudhra intermediate certificate authority private keys—six for TLS and two for code signing—were reported as weak and potentially recoverable, creating an industry-wide trust-store risk rather than a vulnerability in TeamCity itself; eMudhra stated that the affected intermediates had not issued leaf certificates and that it had no evidence of exploitation before disclosure. TeamCity servers and agents may nevertheless trust affected certificates through their Java runtimes or custom certificate stores, while operating systems and browsers are protected after applying vendor updates. JetBrains recommends upgrading to TeamCity 2026.2.2 or 2026.1.6, which add a server health report and updated runtime and Docker-image support, updating Java on every server and agent, reviewing uploaded and agent-specific certificates, and independently updating related tools, container images, and connected services with separate trust stores. TeamCity Cloud has already been updated, but customers must still inspect self-hosted agents and uploaded certificates, and TeamCity CLI users should upgrade to version 1.6.1 or later. The guidance provides verification and manual mitigation procedures for removing compromised eMudhra certificates when Java updates are not immediately possible, with cautions about testing dependent services before altering trust stores.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.