Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Oracle Java eMudhra CA Distrust Update (CVE-2026-91403)

CVE-2026-91403 is Oracle's Java Security Alert of 21 October 2026 that distrusts eMudhra intermediate CA certificates.

Reviewed by
Brandefense Analyst Team
Published
Updated
Reading Time
6 min read
CVE ID
CVE-2026-91403
Vendor
Oracle
Affected Product
Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition (component JSSE)
Exploitation
Not confirmed
Published
21 October 2026

Oracle says the updates distrust a set of intermediate certificate authority (CA) certificates tied to eMudhra, whose private keys were compromised. Oracle scores it CVSS 9.1 in its JSSE risk matrix. No source we read reports the compromised keys being used to intercept traffic, and the CVE is not in the CISA KEV catalog (checked 11 November 2026). A second Oracle alert, CVE-2026-114820, removes the root certificates related to eMudhra, and OpenJDK says to apply that update too.

What it allows

Oracle's alert opens with this description: "This Security Alert addresses CVE-2026-91403 by providing Java updates which distrusts the set of impacted intermediate CA certificates related to eMudhra. To address this CVE, update to the latest Java version or apply the recommended mitigations." It does not describe a code bug. It describes a change to the certificate authorities that Java trusts.

The reason is the eMudhra CA key compromise. OpenJDK says the private keys of eight eMudhra intermediate CA certificates have been compromised. Red Hat explains the risk: a man-in-the-middle attacker could present a certificate for any host name, signed by a weak intermediate, and Java TLS clients would trust it. Our news post on Python, uv and container updates covers software that carries its own CA list.

Why Oracle Scores It 9.1

Oracle lists the issue under the JSSE component, the part of Java that handles secure network connections. Its risk matrix reads network access, low complexity, no privileges and no user interaction, with high impact on confidentiality and integrity and none on availability.

Oracle adds that it can be reached through the JSSE APIs, for example through a web service that passes data to them. It also applies to sandboxed Java Web Start applications and applets that run untrusted code. Red Hat scores the same CVE 6.8 for its products, with high attack complexity and user interaction required.

Why One Update Is Not Enough

Red Hat says OpenJDK first tried to block only the problem intermediate certificates, and that CVE-2026-91403 was assigned to that change. It says the fix "proved insufficient and easy to bypass". OpenJDK then removed the root certificates that signed those intermediates.

Oracle's alert for CVE-2026-114820, published on 24 October 2026, ships that removal. OpenJDK tells users to install it even if they updated their runtime a few days earlier.

Is It Exploited?

No source we read reports the compromised keys being used to intercept traffic. It is not in the CISA Known Exploited Vulnerabilities catalog (version 2026.11.10, checked on 11 November 2026). CISA's entry in the NVD record, dated 23 October, lists exploitation as "none".

Cisco Talos saw no malicious use of the compromised certificates as of 21 October, 14:00 UTC. Cloudflare reported on 30 October that the keys appear to have been used to forge certificates within hours of the weakness becoming public. About 160 handshakes on its outbound connections showed such certificates, naming unrelated domains, but Cloudflare saw no sign of interception. This can change, so check KEV again.

A vulnerability intelligence platform watches the KEV catalog and exploit reports, so you see when that happens.

What Is Not Known Yet

  • Which build Oracle itself names as the fix. Neither alert names one, and the patch availability document is open to Oracle support customers only.
  • An NVD analysis. The record still reads "Awaiting Analysis" and last changed on 24 October.
  • Which other Oracle products that bundle Java will get a patch. Oracle says it keeps adding them to the CVE-2026-114820 alert.

Who is affected

Oracle lists these builds as affected: Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1. Also Oracle GraalVM for JDK 17.0.21 and 21.0.13, and Oracle GraalVM Enterprise Edition 21.3.20.

Oracle tests only versions under Premier Support or Extended Support. It says earlier versions are likely affected too and recommends upgrading to a supported version. The OpenJDK advisory (last updated 26 October) names 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.32.1, 8u504 and earlier.

Fixed Versions

Oracle's alert names no fixed build. For each product it points to a Java SE patch availability document, which is open to Oracle support customers only. Oracle's alert for CVE-2026-114820 lists builds with a .0.2 ending as affected: 8u511-b32, 8u511-perf-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2 and 27.0.1.0.2.

Oracle's public Java downloads page (checked 11 November 2026) offers JDK 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33.0.3 and 8u511 b33, each newer than the builds listed as affected by CVE-2026-114820. The incident tracker at emudhra.we-have-a-problem.com lists the same builds as patched. Neither Oracle alert names a fixed build, so confirm in Oracle's patch document if you have support access.

Timeline

  1. 17 Oct 2026

    An independent researcher reports the weak eMudhra intermediate CA keys to the browser and operating system root programs. eMudhra revokes all eight intermediates the next day, per its statement.

  2. 20 Oct 2026

    Oracle's release notes give 20 October 2026 as the release date of JDK 21.0.13, one of the versions the later alert lists as affected.

  3. 21 Oct 2026

    Oracle publishes Security Alert CVE-2026-91403 as revision 1 and rates it CVSS 9.1. Its description says the Java updates distrust the impacted eMudhra intermediate CA certificates. The alert credits no reporter.

  4. 21 Oct 2026

    The NVD record is published at 22:16 UTC, with Oracle as the source of the CVSS score. Cisco Talos reports no malicious use of the compromised certificates as of 14:00 UTC.

  5. 23 Oct 2026

    CISA's entry in the NVD record lists exploitation for CVE-2026-91403 as none.

  6. 24 Oct 2026

    Oracle publishes Security Alert CVE-2026-114820, whose Java updates remove the impacted root certificates related to eMudhra. OpenJDK's guidance page, last updated that day, names the fix and a check program.

  7. 30 Oct 2026

    Oracle revises the CVE-2026-114820 alert to add more products. Cloudflare reports about 160 handshakes with forged certificates on its outbound traffic and no sign of interception.

  8. 11 Nov 2026

    We re-checked the sources. CVE-2026-91403 is not in CISA KEV (version 2026.11.10), NVD still reads "Awaiting Analysis", and Oracle's Java downloads page offers builds ending in .0.3 (8u511 b33 for Java 8).

What to do

  1. Find where Java runs

    List every system that runs Java, with the exact build. Include application servers, build servers, desktops and products that bundle their own Java. Compare each build with the list in Oracle's alert.

  2. Check whether your runtime trusts eMudhra

    OpenJDK publishes a small program, CheckCerts.java (cr.openjdk.org/~mr/CheckCerts.java), that shows whether a runtime is at risk. It works on JDK 8 and later. It only reads the runtime's trusted certificates; run it with each Java runtime you need to check.

  3. Update Java to a build that fixes CVE-2026-114820

    Install a build whose release notes say they fix JDK-8395690, CVE-2026-114820. OpenJDK says to do this even if you updated recently. For Oracle Java, the patch document needs a support login; match your build against Oracle's alert for CVE-2026-114820.

  4. Use a stopgap if no update exists yet

    OpenJDK offers two: back up the cacerts file, run keytool -delete -cacerts -alias "emsignrootcag1 [jdk]" and the same for emsignrootcag2, emsigneccrootcag3 and comodoaaaca, then restart the runtime. On JDK 8, use -keystore $JDK_HOME/jre/lib/security/cacerts in place of -cacerts. Or turn on revocation checking with -Dcom.sun.net.ssl.checkRevocation=true and -Dcom.sun.security.enableCRLDP=true. Test first: removed roots stop Java trusting certificates that chain to them.

  5. Update Java from your operating system

    Fedora, Arch, Gentoo, Oracle Linux and Red Hat Enterprise Linux builds use the system certificates, so a ca-certificates update is likely enough. On Debian and Ubuntu, also run rm -f /etc/ssl/certs/java/cacerts and update-ca-certificates --fresh as root. FreeBSD and Homebrew packages need a package update.

  6. Check other Java vendors and CA bundles

    The alert covers Oracle Java SE and GraalVM. For a Java build from another vendor, read that vendor's own notice. Python, uv, certifi and container images keep their own CA lists; see the eMudhra incident record.

  7. Watch for changes

    Check Oracle's two alerts, the NVD record and the CISA catalog again over the coming days. Oracle revised the CVE-2026-114820 alert on 30 October, and CISA may add a CVE if exploitation is seen.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-91403?

It is Oracle's Java Security Alert of 21 October 2026. Oracle says it provides Java updates that distrust the intermediate CA certificates tied to eMudhra. Oracle scores it CVSS 9.1 in the JSSE risk matrix.

Am I affected by CVE-2026-91403?

You are if you run one of the Java builds in Oracle's alert and have not applied the Oracle update. A runtime that still trusts the roots related to eMudhra stays exposed, so run OpenJDK's CheckCerts.java. Software with its own CA list, such as pip, uv or certifi, is covered in our eMudhra incident record.

Is CVE-2026-91403 being exploited?

No source we read reports an attack that used the keys to intercept traffic. Cloudflare saw certificates forged with the leaked keys from 20 October, but no interception. The CVE is not in the CISA KEV catalog (checked 11 November 2026), and CISA's NVD entry of 23 October lists exploitation as none.

Which Java versions are affected?

Oracle lists Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, plus GraalVM for JDK 17.0.21 and 21.0.13 and GraalVM Enterprise Edition 21.3.20. Earlier versions are likely affected too.

Where do I get the fix?

Oracle's alert links to a Java SE patch availability document, which needs a support login. It names no fixed build numbers. OpenJDK says to install a build whose release notes name CVE-2026-114820.

How is it related to CVE-2026-114820?

Red Hat says the first Java change, tracked as CVE-2026-91403, proved insufficient and easy to bypass. OpenJDK then removed the root certificates related to eMudhra, and Oracle published that as CVE-2026-114820 on 24 October. Install that update as well.

Is this a code execution flaw?

Oracle's description does not say so. It describes a certificate trust change. The 9.1 score comes from Oracle's risk matrix for the JSSE component, not from a described attack on code.

Is this part of the October 2026 Critical Patch Update?

No. It is a separate out-of-band Security Alert, published on 21 October 2026, a day after the Critical Patch Update of 20 October. It needs its own patching step.

Does it affect Java in the browser?

Oracle says it also applies to sandboxed Java Web Start applications and applets that load untrusted code and rely on the Java sandbox. On servers, Oracle says it can be reached through the JSSE APIs, for example through a web service that supplies data to them.

Sources

  1. Oracle Security Alert Advisory - CVE-2026-91403Oracle
  2. Text Form of Oracle Security Alert - CVE-2026-91403 Risk MatricesOracle
  3. Oracle Security Alert Advisory - CVE-2026-114820Oracle
  4. Compromised Certificates and OpenJDK Java RuntimesOpenJDK
  5. OpenJDK Vulnerability Advisory: 2026/10/21OpenJDK
  6. CVE-2026-91403Red Hat
  7. CVE-2026-91403NVD
  8. Known Exploited Vulnerabilities catalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →