# eMudhra Certificate Compromise (CVE-2026-91403 and CVE-2026-114820): Oracle E-Business Suite Is Affected

- URL: https://www.integrigy.com/oracle-security-blog/emudhra-cve-2026-91403-cve-2026-114820-oracle-ebs
- Published: 2026-10-25
- Type: Blog Post
- Products: Oracle E-Business Suite, Oracle Database
- Focus areas: Vulnerabilities, Oracle Critical Patch Updates
- CVE IDs: CVE-2026-91403, CVE-2026-114820

Note: Updated to include information from the November 2026 CSPU

Oracle E-Business Suite (EBS) is affected by [CVE-2026-91403](https://www.oracle.com/security-alerts/alert-cve-2026-91403.html) and [CVE-2026-114820](https://www.oracle.com/security-alerts/alert-cve-2026-114820.html), the two Java Security Alerts Oracle released in October 2026 for the eMudhra certificate authority compromise. All Oracle EBS 12.2 application tiers run JDK 7, and Oracle Database 19c runs JDK 8. Oracle E-Business Suite also uses Oracle JRE 8 on every desktop to launch Oracle Forms. Every one of these Java installations trusts the compromised certificates until it is updated. The highest risk is on the desktop, where the weak keys can sign a Java Web Start application that the JRE presents as coming from a verified publisher.

## The eMudhra Weak Keys

An error in an April 2025 key ceremony left eight eMudhra P-384 intermediate certificate authority (CA) keys with private values between 4 and 237. Anyone can recover these keys in under a second, and at least one has been published. In May 2025, Sectigo cross-signed the same keys under its AAA Certificate Services root. That root is present in every JDK 7 and JDK 8 trust store Integrigy examined. As a result, a certificate issued with one of these keys chains to a trusted root through either eMudhra or Sectigo. eMudhra revoked the intermediates on October 18 and 19, 2026, and Sectigo revoked its cross-signatures on October 19, 2026.

Oracle released the Java fix in two parts:

| CVE | Released | Java change |
|---|---|---|
| CVE-2026-91403 | October 21, 2026 | Adds the 8 intermediates and the 8 Sectigo cross-signatures to the blocked certificate list (`blacklisted.certs` in JDK 7 and JDK 8) |
| CVE-2026-114820 | October 24, 2026 | Removes the emSign Root CA - G1, emSign Root CA - G2, emSign ECC Root CA - G3, and AAA Certificate Services roots from the `cacerts` trust store |

Oracle rates both CVEs 9.1 under CVSS 3.1. No exploitation against Java has been reported.

## Oracle EBS Application and Database Tiers

Oracle's Java Security Alerts list only the supported Java SE releases. As JDK 7 is in sustaining support, it is not listed in the advisories. JDK 7 is still certified for the Oracle EBS application tier. The emSign roots were added to JDK 7 in 7u411 (January 2024). In addition, every JDK 7 build Integrigy examined trusts AAA Certificate Services. Even an older JDK 7 without the emSign roots therefore trusts the cross-signed keys.

The application tier fix is delivered in [My Oracle Support Patch 34569013](https://support.oracle.com/support/?patchId=34569013) (login required). Oracle re-released the October 2026 Critical Patch Update (CPU) JDK 7 update, 7u521, in that patch on October 24, 2026 as build 1.7.0_521-b32. Integrigy verified that this build removes all four roots and includes the updated blocked certificate list. The November 2026 edition of the Oracle E-Business Suite Java Critical Patch Update Checker (EJCPUC), [My Oracle Support Patch 37171025](https://support.oracle.com/support/?patchId=37171025) (login required), expects [JDK 7u523 on the application tier and JDK 8u513 on the database tier](https://www.integrigy.com/oracle-security-blog/java4shell-cve-2026-114938-oracle-ebs).

Be aware that the fixed and unfixed builds report the same version number. A server that reports 1.7.0_521 may or may not have the fix, which is an unusual property for a version number. EJCPUC compares version numbers only, so it cannot tell the two builds apart.

On the server, the risk is to outbound TLS connections from Oracle EBS, such as payment gateways, bank transmissions, the Workflow Notification Mailer, and OAuth back-channel calls. An attacker who can intercept that traffic can impersonate the remote server. The attacker needs a position on the network path, which limits the risk.

## Java Web Start and Oracle Forms Clients

Organizations that launch Oracle Forms with Java Web Start or the Java Plug-in run Oracle JRE 8 on end-user desktops. The JRE trust store decides both which HTTPS servers to trust and which code signers to trust.

The weak keys can sign code that Java accepts. A CA key can issue a code-signing certificate in any name, including "Oracle America, Inc." or the customer's own company name. The eMudhra intermediates are restricted to TLS, and Windows, Mozilla, and Chrome enforce that restriction. Java does not. Integrigy confirmed in its lab that JDK 7 and JDK 8 accept a code-signing certificate issued by a TLS-only CA. The test used a certificate hierarchy that Integrigy created, not the eMudhra keys.

The primary concern with an un-patched Oracle JRE 8 on the desktop is that an attacker can send a link to a malicious Java Web Start application that the JRE shows as signed by a verified publisher. If the user clicks Run, the application runs with the user's full desktop privileges.

By default, Oracle EBS signs its JAR files with a self-signed certificate created by `adjkey`, so users are accustomed to accepting an unknown publisher warning. A forged certificate shown as verified therefore looks more legitimate than the real one. Fortunately, eMudhra and Sectigo revoked the affected certificates, and Java checks revocation for signed code by default.

## Recommendations

**1. UPDATE THE APPLICATION TIER JDK**

Run the latest version of Oracle E-Business Suite Java Critical Patch Update Checker (EJCPUC), [My Oracle Support Patch 37171025](https://support.oracle.com/support/?patchId=37171025) (login required). Be sure to download the latest version as it is updated periodically and with each Critical Patch Update. You must run EJCPUC on both the application and database tiers. Identify the Java installs that must be updated for the application and database tiers. 

**2. UPDATE THE APPLICATION TIER JDK**

Apply JDK 7u523 (November 2026 CSPU) or later from Patch 34569013. Apply it to all four application tier Java homes on both the run and patch file systems. See [My Oracle Support KA1058](https://support.oracle.com/support/?documentId=KA1058) (login required).

**2. UPDATE THE DATABASE TIER JDK**

Apply JDK 8u513 to `$ORACLE_HOME/jdk` and `$ORACLE_HOME/appsutil/jre`.

**3. UPDATE ORACLE JRE 8 ON DESKTOPS**

Deploy JDK 8u513 or later to every desktop that launches Oracle Forms or has JDK 8 installed.

**4. SIGN ORACLE EBS JAR FILES WITH A PRIVATE CA CERTIFICATE**

Sign the EBS JAR files with a private CA that is distributed to all clients. See [My Oracle Support KB497723](https://support.oracle.com/support/?documentId=KB497723) (login required)

## Java Trust Store Verification

You can verify if the Java Trust Store has the eMudhra or AAA certificates by running the following command against each Java home, including desktop JREs.

```bash
keytool -list -keystore <JAVA_HOME>/jre/lib/security/cacerts -storepass changeit | grep -iE 'emsign|comodoaaaca'
```

If the command returns no output, the trust store is fixed. If any alias is listed, the trust store still trusts the compromised keys.

If you have any questions or need further assistance, please contact us at <info@integrigy.com>.
