On this page (7 sections)

Debian published security advisory DSA-6599-1 on October 31, 2026. It updates the nss package to remove three eMudhra root certificates. The advisory states that it was discovered that several eMudhra intermediate CA certificates have been compromised.

This is not a classic code bug. It is a certificate trust problem, handled by removing roots from the nss package. Anyone running Debian 13 (trixie) servers, build hosts or desktops should apply the update, and anyone whose own website certificate was issued by eMudhra should check their setup.

What the advisory says

The Debian announcement is short. It says it was discovered that several eMudhra intermediate CA certificates have been compromised, and that updated nss packages are provided to remove the three root certificates named above. For the stable distribution, trixie, the fix is version 2:3.110-1+deb13u5, and Debian recommends upgrading your nss packages.

The advisory does not say how the compromise happened, when it occurred, how many certificates were affected, whether any were used to issue fraudulent certificates, or who discovered it. It lists no CVE identifier and no severity score. Only one primary source is available for this story at the time of writing, so treat any further detail you see elsewhere as unconfirmed until the CA or other vendors publish their own statements.

Background: why root removal is used

The following is general background on how certificate trust works, not something the advisory itself describes. Software keeps a list of trusted root CA certificates, and certificates that chain up to a trusted root are normally accepted. Intermediate CA certificates sit between a root and the certificates issued to websites. If an intermediate is compromised, the usual concern is that certificates could be issued that software still trusts. The advisory does not say whether that happened here.

Removing a root from a trust list is a common response because certificates chaining to that root can then stop validating. The same effect can reach legitimate certificates issued under those roots, so the change may cause validation errors for some services. The advisory does not describe such effects, so test rather than assume.

Who is affected

  • Debian 13 (trixie) systems with the nss package installed.
  • Sites and services whose own TLS certificate was issued under one of the three roots named in the advisory. Depending on how a client uses the trust list, such certificates may no longer be accepted after the update.
  • Internal tools and integrations that connect to partners or services using eMudhra emSign certificates.
The advisory names a fixed version for the stable distribution (trixie) only. Check the Debian security tracker page for nss, linked from the advisory, for other releases rather than assuming.

How to check your exposure

First, see which nss packages are installed and at what version. This read-only command lists installed packages whose names contain nss. On trixie, look for an nss package at 2:3.110-1+deb13u5 or newer; confirm the exact package names on the Debian security tracker page for nss.

List installed packages matching nss with their versions (Debian)Shell
dpkg -l | grep -i nss

Second, check whether your own public certificate was issued by eMudhra. This read-only command prints the issuer and expiry date of the certificate your site serves; replace example.com with your hostname. If the issuer mentions eMudhra or emSign, plan to confirm the chain and consider a replacement.

Print the issuer of a site's TLS certificate (any Linux host with openssl)Shell
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -issuer -enddate

The free SSL certificate checker can also show the issuer and chain of your public certificates without logging in to a server.

What to do now

  1. Update the nss package on Debian trixie hosts to 2:3.110-1+deb13u5 or newer.
  2. As a general precaution, restart long-running services and applications that use nss once the update is installed. The advisory does not state that this is required.
  3. Identify any of your own certificates issued under the eMudhra roots named in the advisory and consider a replacement from a different CA if needed.
  4. Test connections to partners and third-party services that may use eMudhra certificates, and watch for new TLS validation errors after the update.
  5. Check other trust stores you run (other operating systems, language runtimes, container base images) for vendor guidance on these roots.
  6. Review the Debian security tracker page for nss for other releases.

This command refreshes package lists and upgrades all installed packages on a Debian host, including nss. Run it as root, and review the proposed package list before confirming.

Update package lists and upgrade installed packages (Debian, run as root)Shell
apt update && apt upgrade
Caution. A trust store change may cause connections to services that use certificates under the removed roots to fail validation. Test in staging where possible, and schedule any service restarts in a maintenance window if they handle critical traffic.

Detection and monitoring afterwards

After patching, watch application logs for certificate verification failures. New failures that name an eMudhra issuer point to a dependency that needs attention. For your own domains, monitor what certificate your site serves so an unexpected change does not go unnoticed; certificate and DNS monitoring can alert on such changes. Certificate Transparency logs are another public place to look for certificates issued for your domains.

If validation errors appear after a CA change, our guide on fixing Not secure and SSL errors can help with troubleshooting.

What is still unknown

  • Whether any compromised intermediate was used to issue fraudulent certificates.
  • The timeline and cause of the compromise.
  • Whether other vendors (browsers, operating systems) have removed or distrusted the same roots.
  • Why the advisory lists the third root as "emSign ECC Root CA - C3" without the eMudhra prefix used for the other two; the names are quoted here exactly as written in the advisory.

We will treat the story as developing. Until more primary sources appear, the safe course is the one Debian recommends: upgrade your nss packages.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6599-1] nss security updatelists.debian.org ·
  • Debian
  • nss
  • certificate authority
  • TLS
  • eMudhra
  • trust store