CVE-2026-91403 eMudhra Revocation: Checking Your Exposure

Before patching anything, find out which of your trust stores, runtimes and container images would actually notice an eMudhra revocation, and which would silently ignore it.

Binary Buddies · 5 min read · 9 views

An Oracle Security Alert Advisory tagged CVE-2026-91403 and tied to eMudhra certificate revocation is circulating. For engineering teams, the practical question is narrow: does anything we run trust a certificate chain from eMudhra, and what changes for us if some of those certificates are no longer valid?

We could not verify the substance of the advisory. The material available to us when writing this does not contain the advisory text. It does not say which products are affected, which certificates are revoked, what the severity score is, or which patch versions fix it. We are not going to fill those gaps with guesses. If you need affected versions or fix dates, read Oracle's advisory page directly and treat any second-hand summary that quotes numbers with suspicion until you have checked it.

The rest of this article covers what you can do without those details: find where a given certificate authority is trusted across your stack, check whether revocation is actually enforced there, and avoid the fixes that make things worse.

What we know and what we don't

Confirmed: an advisory exists under this identifier, and its subject is revocation of certificates associated with eMudhra, a certificate authority. That is enough to start an inventory. It is not enough to tell you whether you are exposed.

Not confirmed, at least by anything we could check:

  • Which Oracle products or JDK builds the advisory covers
  • Whether the revocation covers a root, an intermediate, or individual leaf certificates
  • Whether Oracle is removing a root from a bundled trust store or only publishing revocation data
  • Any CVSS score, release date, or fixed version

These distinctions change your response a lot. Removing a root breaks every chain beneath it, everywhere that store is used, on the next update. Revoking individual leaves only affects clients that actually check revocation, and many don't. Until you know which case applies, plan for both.

Map where the CA could be trusted

Most stacks have more than one trust store, and they rarely agree with each other. A typical web or ERP deployment has an operating system bundle and a JVM cacerts file if anything Java-based is involved. Python services often ship their own CA bundle through certifi, and container base images carry their own copy of the OS bundle, frozen at build time.

Odoo deployments are a good example. Odoo's outbound integrations, such as payment providers, shipping carriers and e-invoicing gateways, run through Python HTTP libraries. Which bundle they use depends on how the environment was built, not on what the host OS has. An OS-level update does nothing for a service pinned to an old certifi inside a virtualenv or image.

List every place a TLS client runs, inbound and outbound, before you touch anything. Missing one store is how half your services follow a trust change and the other half quietly don't.

Inventory commands

These are standard tools. Search subject and issuer fields, not only filenames. CA certificates are not always filed under the company's legal name, so a filename grep can come back empty even when the CA is present.

# JVM trust store (Java 9+). The default password is commonly 'changeit'
keytool -list -v -cacerts -storepass changeit | grep -i -B2 -A6 emudhra

# Python services: find the bundle actually in use
python3 -c 'import certifi; print(certifi.where())'
grep -i -c emudhra "$(python3 -c 'import certifi; print(certifi.where())')"

# Inspect a live endpoint's chain
openssl s_client -connect partner.example.com:443 -showcerts </dev/null \
  | openssl x509 -noout -subject -issuer

The last command only shows the leaf. To see every issuer in the chain, save the full -showcerts output and run each certificate block through openssl x509 -noout -issuer. Run this against your outbound dependencies as well as your own hosts. Your own certificates may come from a different CA while a supplier's API depends on the one in question.

Revocation is not enforced everywhere

A revoked certificate only fails where a client checks revocation and treats a failed check as fatal. Many TLS clients either skip OCSP and CRL checks or soft-fail: if the revocation responder can't be reached, the connection goes through anyway. So 'revoked' and 'rejected' are not the same thing across your fleet.

In practice, a revocation-only change may produce no errors at all in some services and hard failures in others, depending on library and configuration. Do not read a quiet log as proof you are unaffected. Test explicitly, with revocation checking turned on, from the same runtime and image the service runs in production.

If the advisory turns out to involve trust store removal rather than revocation data alone, the behaviour flips. Failures become immediate and consistent after the update lands, usually showing up as chain-building or 'unable to find valid certification path' errors in Java clients.

Where this approach does not fit

This playbook assumes you control the TLS clients. It does nothing for third-party SaaS or managed runtimes whose trust stores you can't inspect. For those, ask the vendor directly, and get the answer in writing.

Watch for these:

  • Disabling verification to clear errors. Setting verify=False, adding trust-all managers, or dropping hostname checks turns a certificate problem into an open interception risk. It also tends to survive long after the incident.
  • Manually re-adding a removed root. If a root was pulled deliberately, re-importing it into cacerts undoes the protection the advisory exists to provide.
  • Patching the host but not the image. Rebuild containers. A host-level bundle update does not reach a frozen base layer.
  • Acting on unverified specifics. Scope the work to what Oracle's own advisory states, not to summaries, including this one, until you have read it.

The inventory is worth doing whatever the advisory turns out to say. The next CA incident will ask the same question, and a current map of your trust stores turns it from a week of guesswork into an afternoon.

  • #CVE-2026-91403
  • #Oracle security alert
  • #certificate revocation
  • #eMudhra
  • #security
  • #trust store

Comments

Add a comment
Sign in with Google to join the conversation