IntroductionThe private keys of the eMudhra Certificate Authority (CA) have been demonstrated on 20 October 2026 to have been compromised. The Ubuntu Security Team has released updates to the system PKI (Public Key Infrastructure) root CA store in the ca-certificates package.While the eMudhra CA is not directly trusted as a root on Ubuntu, two other root CAs have cross-signed the eMudhra CA: emSign Root TLS CA – G3 and Comodo AAA Certificate Services. These two roots have been removed from the Ubuntu trusted root store in the ca-certificates package to ensure that the compromised eMudhra CA is no longer trusted. Any legitimate certificate which is ultimately trusted by either of these two root CAs would no longer be trusted. It is unlikely, but this may result in some hosts being unreachable, due to their use of the revoked certificate. The AAA Certificate Services CA had previously been removed from the CA bundles in Ubuntu 22.04 (Jammy Jellyfish) and newer releases.Which Ubuntu releases are affected?ReleasePackage NameRemediation statusTrusty (14.04)ca-certificatesFixed in 20230311~14.04.1~esm3Xenial (16.04)ca-certificatesFixed in 202402031~16.04.1~esm3Bionic (18.04)ca-certificatesFixed in 202402031ubuntu0.18.04.1+esm3Focal (20.04)ca-certificatesFixed in 20240203~20.04.1ubuntu0.1~esm2Jammy (22.04)ca-certificatesFixed in 20260816ubuntu0.22.04.1Noble (24.04)ca-certificatesFixed in 20260816ubuntu0.24.04.1Resolute (26.04)ca-certificatesFixed in 20260816ubuntu0.26.04.1Stonking (26.10)ca-certificatesFixed in 20260816ubuntu0.26.10.1How to check if you are impactedYou can verify the version of the ca-certificates package with the following command:dpkg -l 'ca-certificates' | grep ^iiImpact of the CA CompromiseAn unauthorized third party would be able to sign fraudulent X.509 certificates; these would pass validation by a TLS implementation (commonly TLS clients) that trusts the eMudhra CA. Mitigations such as public key pinning or DNS Certificate Authority Authorization (CAA) records do provide the ability to detect such fraudulent certificates, but depend on the TLS application making use of the mitigations and are not widely used.This could lead to the identity impersonation of a TLS endpoint and could allow an attacker-in-the-middle to intercept and compromise the confidentiality and integrity of TLS connections, irrespective of the CA that the authentic TLS endpoint uses, unless mitigations are employed.How to apply fixesWe recommend you upgrade all packages:sudo apt update && sudo apt upgradeIf this is not possible, the affected component can be targeted:sudo apt update && sudo apt install --only-upgrade ca-certificatesThe unattended-upgrades feature is enabled by default for Ubuntu 16.04 LTS onwards. This feature: Applies new security updates every 24 hours automatically.If you have this enabled, the patches above will be automatically applied within 24 hours of being available.Ubuntu 26.10, 26.04 LTS, 24.04 LTS, and 22.04 LTS receive these fixes as part of standard support. If you are using Ubuntu 20.04 LTS or older, you can apply this fix with an Ubuntu Pro subscription via the Expanded Security Maintenance (ESM) service. Ubuntu Pro is free for up to 5 machines, or up to 50 machines for community members. Ubuntu Pro also provides access to Landscape which enables you to control the roll-out of security fixes across your estate. Learn more. Note for Ubuntu Desktop usersOn Ubuntu Desktop, the most common TLS client would be a browser. They are typically installed as snap packages on Ubuntu desktop, and do not use the system trust store provided by the ca-certificates package. Snap packages are refreshed four times a day by default. If you have disabled automatic updates, ensure that you refresh your snaps manually.Referenceshttps://ubuntu.com/security/notices/USN-8944-1https://ubuntu.com/security/notices/USN-8944-2https://emudhra.we-have-a-problem.com/