Oracle has released Java security updates addressing the eMudhra certificate security issue and additional Java vulnerabilities. Oracle Integration customers should review affected endpoint certificate chains and update the JDK used by connectivity agents, as described below.

This guidance applies to Oracle Integration customers who:

  • Invoke endpoints using affected certificates: Review the complete TLS certificate chains of endpoints invoked by your integrations and replace affected chains promptly, as described in Action 1. See Oracle’s certificate guidance for details.
  • Run connectivity agents using affected Oracle JDK 17 releases: Review installations running 17.0.21, 17.0.21.0.2, or 17.0.21.0.3 and promptly update to 17.0.21.1 (full version 17.0.21.1+4) or a later applicable supported JDK 17 security update. See the November 2026 Critical Security Patch Update advisory and Oracle JDK 17.0.21.1 release notes. 

Action 1 – Replace Affected Endpoint Certificate Chains Immediately

Which certificates are affected

Oracle’s JDK security update removes the following root certificates from the default cacerts trust store:

emSign Root CA – G1eMudhra Technologies Limitedemsignrootcag1 [jdk]
emSign Root CA – G2eMudhra Technologies Limitedemsignrootcag2 [jdk]
emSign ECC Root CA – G3eMudhra Technologies Limitedemsigneccrootcag3 [jdk]
AAA Certificate ServicesComodo CA Limitedcomodoaaaca [jdk]

See Oracle’s certificate guidance for the current certificate list and remediation instructions.

The underlying security issue involves compromised intermediate CA certificates. As part of the remediation, Oracle’s Java update removes the root certificates listed above from its default trust store. Their removal does not, by itself, indicate that those roots’ private keys were compromised.

An endpoint requires remediation if its certificate chain uses a compromised intermediate certificate or depends on one of the affected root certificates listed above.

What to replace at affected endpoints

Work with your endpoint administrator or certificate provider to identify endpoints whose TLS certificate chains depend on the affected certificates listed above.

For each affected endpoint:

  1. Obtain an unaffected certificate chain. Your certificate provider can determine whether the endpoint needs a newly issued TLS server certificate, an updated intermediate certificate chain, or both. The replacement chain must exclude the compromised intermediate certificates and must not depend on the removed root certificates. Renewing a certificate under the same affected chain will not resolve the issue.
  2. Install the replacement at the endpoint. Configure the server certificate and required intermediate certificates on the application server, load balancer, or API gateway that serves the endpoint’s HTTPS connection.
  3. Test the connection and integrations.
    • Direct connections from Oracle Integration: Test the connection and run the dependent integration flows. Validate the certificate changes in non-production before applying them to production.
    • Connections through a connectivity agent: Test the connection and dependent integration flows using an agent running the updated JDK described in Action 2.

Begin remediation immediately and complete endpoint certificate changes and validation promptly. Coordinate agent JDK updates with the endpoint changes and validate in non-production environments first.

Action 2 – Update the JDK Used by Connectivity Agents

Oracle’s security advisories address the eMudhra certificate-trust issue and additional Java vulnerabilities. Customers running Oracle JDK 17.0.21, 17.0.21.0.2, or 17.0.21.0.3 should update the JDK used by their connectivity agents.

Update to Oracle JDK 17.0.21.1 (full version 17.0.21.1+4) or a later applicable supported JDK 17 security update. Older JDK 17 releases also require review and should not be assumed to be unaffected. Apply the update promptly and validate dependent integrations.

Customers are responsible for updating the JDK installed on connectivity-agent hosts. Follow these steps:

  1. Identify the JDK used by each agent. Check the agent’s startup or service configuration to confirm the actual JDK installation in use.
  2. Review certificate stores. Check the JDK’s cacerts, certificates imported into the connectivity agent’s agenthome/agent/cert/keystore.p12, and any other explicitly configured custom trust stores against Oracle’s certificate guidance. Updating the JDK does not automatically remediate separately maintained certificate stores.
  3. Update and validate non-production first. Apply the JDK update, restart the agent using the updated JDK, and test agent connectivity and dependent integrations.
  4. Update production after successful validation. Apply the update to each production agent host and verify connectivity and dependent integrations.

For details about the fix and the recommendation to keep the JDK current, see the JDK 17.0.21.1 release notes.

Additional information and assistance

If you need assistance identifying the applicable update or investigating connectivity issues, open a Service Request with Oracle Support.