Erkan Ozdogan.
Security

One compromised CA, many trust stores: what the October 2026 Node.js, Java and BIND releases mean for your applications

9 min readTürkçe oku

Last updated:

One compromised CA, many trust stores: Node.js, Java and BIND for developers

When a certificate authority fails, browsers usually fix it for everyone within days. Applications are slower, because most of them do not use the browser’s trust list. The eMudhra incident of October 2026 is a clean example: Chrome blocked the compromised intermediates on 17 October, but Node.js and Java only shipped their fixes on 21 October, and anything with its own trust store waits for its own update.

TL;DR

  • Eight eMudhra intermediate CAs were blocked after their keys proved weak; browsers acted from 17 October, Node.js and Java on 21 October.
  • Your application trusts certificates through several independent lists: the OS bundle, JDK cacerts, Node.js’s built-in roots, certifi and container images.
  • Node.js 22.23.4, 24.22.1 and 26.12.1 removed the intermediates from their bundled list; Java needs the build named in CVE-2026-91403.
  • Custom stores such as NODE_EXTRA_CA_CERTS files are never cleaned by a runtime release.
  • Add a CI test that expects a distrusted chain to fail.

What happened to eMudhra

On 17 October a researcher reported to Mozilla that the private keys of eight eMudhra intermediate CAs were compromised, and signed the same message with each of them as proof. eMudhra later explained that a flaw in its key generation process had produced a second, weak set of keys alongside the strong ones, and that the weak keys were the ones published to root programs in April 2025. With those keys an attacker could issue a valid-looking certificate for any domain. Chrome, Apple and Microsoft blocked the intermediates between 17 and 20 October and Mozilla shipped the block in NSS.

Where trust lives in your application

Where your application finds its trustEACH STORE IS UPDATED SEPARATELYeMudhra8 INTERMEDIATESCOMPROMISEDBROWSERSBlocked 17 to 20 OctoberOS BUNDLEca-certificates packageJAVA CACERTSJDK build in CVE-2026-91403NODE.JS BUILT-IN22.23.4 / 24.22.1 / 26.12.1PYTHON CERTIFIcertifi package updateCONTAINER IMAGESRebuild with --pullSOURCES: MOZILLA, NODEJS.ORG, ORACLE
Trust stores an application uses and how each one is updated

A typical service trusts certificates through several independent lists. The operating system bundle covers curl, PHP and most Linux tools. Java uses the cacerts file inside each JDK. Node.js uses a CA list compiled into the binary unless you pass --use-system-ca. Python’s requests uses certifi. Container images carry whatever bundle was current when they were built. Updating one of these leaves the others unchanged.

How do you inspect each trust store?

Trust store Used by How to inspect it How it is updated
Operating system bundle curl, PHP, most Linux tools trust list (Red Hat family) or the files under /etc/ssl/certs ca-certificates package
Java cacerts Every JVM using that JDK keytool -list -cacerts JDK update, or keytool edits
Node.js built-in list Node.js unless --use-system-ca node -p "require('tls').rootCertificates.length" Node.js release
Python certifi requests and many libraries python -m certifi prints the bundle path certifi package release
Container image Everything inside the image The same commands, run inside the container Rebuild from an updated base

Map your own service’s stores:

A field note: what a server’s own list shows

On 23 October we listed the operating system trust store on one of our CloudLinux servers and found six entries with emSign in the name. That is not by itself a sign of exposure: the compromised certificates were intermediates, and roots of the same family can legitimately appear in a bundle until a vendor decides otherwise. It is a reminder that a quick grep answers “is this name present”, not “am I protected”, and that the answer for the same machine differs for curl, Java and Node.js, because each reads a different list.

What about Python, Go, PHP and other runtimes?

The pattern holds beyond Node.js and Java, with different defaults. Go on Linux reads the system certificate files, so it follows the operating system bundle. PHP’s cURL and stream functions use the system bundle unless openssl.cafile or curl.cainfo points elsewhere. Python’s ssl module uses the system store, but the popular requests library uses certifi, so two parts of the same Python application can trust different lists. Ruby and .NET on Linux generally use the system store through OpenSSL.

The practical rule is not to memorize this table but to ask, for every client library you use, which file it actually opens. A configuration value or environment variable that redirects it to a private bundle is the most common reason a fleet-wide update misses a service.

Node.js: the fixes beyond the headline

The previous post covered the four high-severity fixes in 22.23.4, 24.22.1 and 26.12.1. The rest of the release also deserves a look from anyone writing network code.

  • Bundled CA store. The eMudhra intermediates are gone, which is the only fix for services that rely on Node’s built-in roots.
  • CVE-2026-105481, medium. A keep-alive socket could process a response written before its request was sent, which can attach the wrong response to a request in clients that reuse connections.
  • CVE-2026-106072, medium. Non-canonical IPv4 hostnames let a certificate’s DNS name authenticate an IP endpoint.
  • CVE-2026-106070, low, 26.x. ZipFile could return attacker-controlled prefix bytes after failed header validation.
  • CVE-2026-106071 and CVE-2026-106073, low. Two more Permission Model gaps, one through a wildcard lookup and one through fs.realpathSync. Treat the Permission Model as a guard rail, not a sandbox.
  • Dependencies. Updated c-ares, OpenSSL and Undici, so fetch() and DNS behavior change slightly with the upgrade.

Java: the alert after the update

Oracle’s Critical Patch Update on 20 October carried 55 Java SE fixes, 49 of them remotely exploitable without authentication. On 21 October Oracle added Security Alert CVE-2026-91403, rated 9.1, for JSSE: Java could keep accepting certificates from the compromised eMudhra intermediates. Reports list builds from the October update itself among those affected, so applying the quarterly update is not enough. Install the build named in the alert, then confirm with keytool -list -cacerts that the eMudhra entries your release should drop are gone.

BIND: when DNS is part of your stack

ISC’s 21 October release fixed four high-severity BIND 9 issues; the fixed versions are 9.20.30 and 9.21.27. Most developers never touch named, but two cases are common. If your environment uses GSS-TSIG for dynamic DNS updates, usually through Active Directory or Kerberos, CVE-2026-94300 can corrupt memory and has no workaround. If you ship BIND inside a container image for local development, tests or a sidecar resolver, the image has to be rebuilt to pick up the fix.

How do you roll a trust change through many services?

A trust-store change is unusual because it can break things in both directions. Remove a certificate too early and a service that still talks to a partner with an affected chain starts failing; leave it too long and the service keeps trusting keys that are known to be compromised. A short sequence keeps both risks visible.

  1. Find who you talk to. List the outbound TLS endpoints of each service and check which of them, if any, present a chain through an affected eMudhra intermediate. Usually none do, and knowing that makes the rest safe.
  2. Update the runtimes in a canary. Deploy the new Node.js or Java build to one instance, watch for handshake failures for an hour, then continue.
  3. Clean the custom stores. Remove the affected intermediates from any file passed through NODE_EXTRA_CA_CERTS and from any custom Java trust store, since no runtime release touches those.
  4. Keep the test. Add the distrusted-chain test from the checklist below to CI, so a future rebuild from an old base image fails instead of quietly trusting the old chain again.

Checklist for your code and pipeline

  1. List your trust stores. For each service, write down which bundle it actually uses: OS, JDK cacerts, Node.js built-in, certifi or a file in the image.
  2. Upgrade the runtimes. Node.js 22.23.4, 24.22.1 or 26.12.1; the Java build named in CVE-2026-91403; BIND 9.20.30 or 9.21.27 where you ship it.
  3. Rebuild images with --pull. A stale base image keeps the old CA bundle no matter what the host runs.
  4. Do not trust custom CA lists blindly. If you pass NODE_EXTRA_CA_CERTS or maintain your own cacerts, remove the eMudhra intermediates there yourself.
  5. Check what you serve and pin. Reissue any certificate that chains to an affected eMudhra intermediate, and update certificate pins in mobile apps or service clients before the old chain stops validating.
  6. Add a trust test to CI. A small test that connects to a known endpoint with a revoked or distrusted chain and expects failure catches a stale bundle before production does.

The short version

Certificate authorities fail rarely, but when they do the cost lands on whoever has the most trust stores. Most applications have more than their developers think, spread across runtimes, libraries, environment variables and images. Mapping them once, keeping custom stores small, and testing that a distrusted chain really fails turns the next incident into an update rather than a hunt.

FAQ: the eMudhra compromise and your trust stores

Why did browsers block the eMudhra intermediates days before Node.js and Java did in 2026?

Browsers can push revocations and distrust lists to every installation without a full release. Node.js and Java carry their trust lists inside the runtime, so their fixes needed new releases, which arrived on 21 October.

OS ca-certificates vs runtime trust stores: is the OS update enough for Java and Node.js apps?

No. Java uses the cacerts file inside its JDK and Node.js uses its built-in list by default, so an operating system update does not change what either trusts. Update each runtime as well.

Does NODE_EXTRA_CA_CERTS need attention after the eMudhra compromise?

Yes, if the file you pass contains any eMudhra intermediates. Node.js trusts everything in that file in addition to its built-in list, so a release that removes them from the built-in list does not remove them from your file.

How do you check a JDK’s cacerts for eMudhra certificates with keytool?

Run keytool -list -cacerts and filter the output for emSign or eMudhra. Compare the result with what the JDK build named in Security Alert CVE-2026-91403 is expected to contain, and update the JDK rather than editing a shared store by hand.

What should mobile apps that pin certificates do after the eMudhra incident?

If any pinned certificate or key chains to an affected intermediate, ship an app update with new pins before the old chain stops validating, and keep a backup pin for a different CA so the next incident does not lock users out.

What does CVE-2026-105481 mean for Node.js clients that reuse keep-alive connections?

A keep-alive socket could process a response written before its request was sent, so a client reusing connections could match the wrong response to a request. Update Node.js and avoid sharing connection pools across unrelated tenants or users.

Why does CVE-2026-106072 matter for code that connects to IP addresses over TLS?

Non-canonical IPv4 forms could let a certificate’s DNS name authenticate an IP endpoint. If your code connects to IP literals, normalize them to the canonical dotted form before connecting, and verify that the certificate carries the IP as an IP SAN.

Does a BIND container used for local development need the October 2026 update?

Yes, if it is reachable by anything you do not fully control, such as a shared development network. Rebuild the image on BIND 9.20.30 or 9.21.27, and keep development resolvers off public interfaces.

How do you write a CI test that catches an outdated trust store?

Connect from the built image to an endpoint whose certificate chain is known to be distrusted and assert that the connection fails, then to a known-good endpoint and assert that it succeeds. Run both against every trust store the service uses.

Oracle October 2026 CPU vs Security Alert CVE-2026-91403: is the quarterly update enough for Java?

No. Security Alert CVE-2026-91403 came a day after the update, and reports list October builds among those affected. Install the build the alert names, then confirm with keytool that the trust store changed.

The server side of the same week is in Node.js, BIND and Java in one week, and the PHP2Shell release is covered in PHP2Shell for developers.

Sources