Following Debian’s update to its system-wide trust store removing two compromised root certificates, an audit has found over 100 Debian packages still bundling those distrusted certificates internally. This discovery exposes how some applications remain vulnerable even after core security fixes are deployed.
What Debian Changed — and Why It Matters
On October 20, Debian pulled the emSign ECC Root CA – G3 and Comodo AAA Services root certificates from its central trust store. These were removed as part of security measures after related eMudhra intermediate certificates were breached. This change was introduced through the updated ca-certificates package — version 20250419+deb13u1 for Debian 13 “trixie” and version 20250419~deb12u2 for Debian 12 “bookworm”.
The removal affects what certificates applications will accept — but only for software using Debian’s shared trust store. Applications that include their own certificate bundles skip the revised trust store and thus may continue to accept certificates that Debian now rejects.
Audit Reveals Pervasive Gaps in Trust Enforcement
A scan conducted by Debian developer Steve McIntyre on a local Debian mirror, supplemented by custom signature checks by Enrico Zini, uncovered more than 100 instances of packages that still contain the distrusted root certificates. Detections appeared in packages tied to tools and ecosystems such as Python’s pip, Node.js, AWS utilities, Qt WebEngine, gRPC, and the Network Security Services (NSS). Some matches were in legacy samples or outdated versions, but many are still part of currently deployed software.
The findings underscore that updating the central trust store doesn’t automatically immunize all software. Bundled certificate files in containers, Flatpaks, or programming environments like virtualenvs might override or bypass the shared store entirely.
What Administrators Can Do Now
Organizations running Debian should first ensure their system has the latest ca-certificates package for their release. But that’s not enough: teams must also check which trust materials their applications are using — especially those responsible for HTTPS connections, cloud credentials, or software downloads.
Where possible, applications ought to rely on the system-wide trust store rather than shipping private copies of CA certificates. If software still includes its own certificate files, investigate whether they are actually loaded at runtime. Where feasible, rebuild packages or swap bundled copies for symbolic links pointing at the system trust store to ensure security updates apply uniformly.
Broader Implications
This situation illustrates a long-standing challenge in security architectures: decentralization of certificate trust can introduce gaps that undermine systemwide updates. Shared security fixes have limited reach when applications bake in their own trust material. It also highlights the maintenance burden for downstream dependencies — even when the core OS is up to date, those gaps can persist unnoticed.
The wider software community — Debian package maintainers included — must treat system trust store updates as critical events. Proactive audits, rebuilds, and configuration changes will be essential to ensure the distrust of compromised CAs is enforced everywhere.