Over 100 Debian Packages Still Contain Distrusted CA Certificates Despite Security Updates

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


A scan of a Debian package mirror found that more than 100 packages still contained copies of distrusted certificate authority (CA) certificates after Debian removed them from its system trust store.

Debian developer Steve McIntyre posted the scan results to the Debian developer mailing list on November 19. The findings show why updating the operating system’s trust store does not necessarily change which certificates an application accepts.

On October 20, Debian removed the emSign ECC Root CA – G3 and Comodo AAA Services root certificates after several eMudhra intermediate CA certificates were compromised. Debian fixed its shared ca-certificates package in version 20250419+deb13u1 for Debian 13 “trixie” and 20250419~deb12u2 for Debian 12 “bookworm.”

Unlike a Debian kernel security update, this fix changes which certificate chains applications accept, but only if they use the updated trust store.

Distrusted CA Certificates Remained

A trust store is a list of certificates an application relies on to verify the identity of a server before making an encrypted connection. Debian provides a shared list through ca-certificates, but some packages ship their own copies.

An application that relies on a separate list can still accept a certificate chain that another application on the same machine rejects. This is distinct from the changes covered in our report on shorter Let’s Encrypt TLS certificate lifetimes, which concern when server certificates expire.

Debian developer Enrico Zini drew attention to the issue after using custom ClamAV signatures to look for the certificates on systems he had installed. His scan found copies in packages or files tied to pip, Node.js, gRPC, NSS, AWS tools, and Qt WebEngine.

McIntyre then widened the search to his local Debian mirror. Some matches were in sample code or older package versions, so the results do not show that every match represents a currently installed application that still trusts either root.

Administrators should install the latest ca-certificates update for their release and check which trust store their applications actually use. Start with services that make outbound HTTPS connections and tools that download software or handle cloud credentials. Check containers, Flatpaks, and Python virtual environments separately.

Updating the host does not necessarily replace certificate files shipped inside them. Use Debian’s security advisories and package tracker to verify the installed version and follow related updates.

McIntyre argued that Debian packages should use the shared system trust store instead of shipping their own. Other developers discussed rebuilding packages or replacing bundled copies with links to the system store where possible.

That would let future distrust updates reach more applications through one package. Until then, a file match is a starting point: verify whether the running application loads that file before deciding whether it needs a separate fix.

What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

The post Over 100 Debian Packages Still Contain Distrusted CA Certificates Despite Security Updates appeared first on Cyber Security News.