Over 100 Debian Packages Retain Distrusted CA Certificates
More than 100 Debian packages were found to contain distrusted CA certificates, bypassing system-wide security updates and potentially allowing compromised certificate chains.

A recent scan of a Debian package mirror has revealed a significant security oversight: over 100 packages still contain copies of distrusted certificate authority (CA) certificates, even after Debian had removed them from its system trust store. This discovery, shared by Debian developer Steve McIntyre on the developer mailing list, highlights a critical gap in how software packages manage their own security configurations, potentially leaving systems vulnerable.
The issue stems from the fact that while Debian maintains a central ca-certificates package for its system trust store, some individual packages bundle their own independent copies of CA certificates. This means that even if the system's trust store is updated to distrust a compromised CA, applications relying on these bundled certificates may continue to trust them. This was particularly relevant after Debian removed the emSign ECC Root CA – G3 and Comodo AAA Services root certificates on October 20, 2026, due to compromises in several eMudelta intermediate CAs.
While Debian released updates for its ca-certificates package for Debian 13 "trixie" and Debian 12 "bookworm" to reflect these changes, the problem persists for packages that do not utilize the system's shared trust store. Applications that rely on these separate, bundled certificate lists could still accept connections secured by compromised certificate chains, creating a blind spot for security administrators.
Developer Enrico Zini first brought attention to the problem using custom ClamAV signatures to detect the presence of these distrusted certificates. His initial findings indicated their presence in packages related to widely used tools and libraries such as pip, Node.js, gRPC, NSS, AWS tools, and Qt WebEngine. McIntyre's subsequent, broader scan confirmed the widespread nature of this issue across the Debian mirror.
It is important to note that not every match found in the scan necessarily represents an actively exploited vulnerability. Some findings were in sample code or older package versions. However, the presence of these certificates indicates a potential risk that needs careful assessment by system administrators.
To mitigate this risk, administrators are advised to ensure their systems have the latest ca-certificates updates installed for their respective Debian releases. Crucially, they must then investigate which trust store their specific applications are using. Particular attention should be paid to services making outbound HTTPS connections, tools that download software, and those handling cloud credentials. This also extends to containerized environments, Flatpaks, and Python virtual environments, as updating the host operating system does not automatically update certificates bundled within these isolated environments.
McIntyre and other Debian developers are discussing potential long-term solutions, including rebuilding packages to exclusively use the shared system trust store. This would ensure that future updates to the trust store are automatically applied to all applications relying on it. Until such a systemic fix is implemented, administrators must manually verify whether running applications are loading the bundled, potentially distrusted, certificate files and apply specific fixes as needed.