Silverblaze
Silverblaze Security Bulletin – CVE-2026-91403 / CVE-2026-114820

Security advisories

Security Bulletin: Java Trusted Certificate Update (eMudhra)
CVE-2026-91403 and CVE-2026-114820

Published November 18, 2026 · Updated November 20, 2026
Check recommended
Status: Action may be required, depending on the Java version on your portal server.
Where the issue is: Third-party: Java
Silverblaze Cloud-hostedCustomer-managed
Silverblaze PortalFixed
No action required. Silverblaze has updated your environment.
Check recommended
We recommend checking your Java installation using the steps below.
SmartFormsNot applicableCheck recommended
We recommend checking your Java installation using the steps below.
Silverblaze ACE
Multi-tenant SaaS on Microsoft Azure
Not affected
Does not use Java.
Not applicable

Summary

In October 2026, Oracle and the other Java vendors released security updates (CVE-2026-91403 and CVE-2026-114820) after several certificate authorities operated by eMudhra were found to be compromised. The updates remove the affected root certificates from Java's list of trusted certificates. On a server that hasn't been updated, someone able to intercept its network traffic could potentially pose as a system the portal connects to, such as your billing system, meter data system, payment provider or email service. The issue is in Java, not in the Silverblaze Portal, SmartForms or Apache Tomcat, and does not affect your customers' web browsers. There are no known reports of exploitation.

Assessment

A server is affected if the Java used by Apache Tomcat still trusts the removed certificates, which is the case until Java has been updated. Silverblaze Cloud-hosted environments, where we manage the server and its patching for you, have been updated. Environments managed by your own IT team, on-premise or in your own cloud, may be affected depending on when Java was last updated. This applies to the Silverblaze Portal and to SmartForms. We recommend your IT team check using the steps below.

Silverblaze ACE does not use Java and is not affected.

How to Check (customer-managed environments)

  1. Find the Java folder that Tomcat uses.
    • Windows: in the Tomcat bin folder, open tomcat9w.exe and go to the Java tab. The Java folder is the part of the Java Virtual Machine path before \bin.
    • Linux: run ps -ef | grep [c]atalina. The Java folder is the part of the first path before /bin/java.
  2. Run the check from that Java folder's bin folder. Replace <cacerts> with ..\lib\security\cacerts on Windows or ../lib/security/cacerts on Linux (for a Java 8 JDK, add jre before lib), and <truststore password> with your truststore password (Java's default is changeit).
    • Windows (PowerShell):
      .\keytool.exe -list -v -keystore "<cacerts>" -storepass "<truststore password>" | Select-String -SimpleMatch "Your keystore contains","Owner: CN=emSign ECC Root CA - G3","Owner: CN=emSign Root CA - G2","Owner: CN=AAA Certificate Services"
    • Linux:
      ./keytool -list -v -keystore "<cacerts>" -storepass "<truststore password>" | grep -E "^(Your keystore contains|Owner: CN=(emSign ECC Root CA - G3|emSign Root CA - G2|AAA Certificate Services))"

If the output shows only the line "Your keystore contains…", the server is not affected and no action is needed. If any line starting with "Owner:" appears, follow the steps below. If nothing appears at all, the folder or password is incorrect; correct it and run the check again.

The check doesn't look for "emSign Root CA - G1". Some updated Java builds, such as Eclipse Temurin, still include it, so finding it doesn't mean a server is affected. The interim fix below removes it along with the other three, following OpenJDK's guidance.

If the Server Is Affected

  1. Install the latest update for the Java version you already use, from the same vendor. Do not change to a different major Java version. For example, Oracle Java 8 should be updated to Oracle Java 8 Update 511 (build b34) or later, available from My Oracle Support. For other vendors, the update's release notes should list JDK-8395690 or CVE-2026-114820.
  2. If Java was installed from a Linux package, update the Java and ca-certificates packages. On Debian or Ubuntu, then rebuild the Java certificate store, as updating the packages alone is not enough:
    sudo rm -f /etc/ssl/certs/java/cacerts
    sudo update-ca-certificates --fresh
  3. If the update was installed to a new folder, update the Java path on the Java tab of tomcat9w.exe (Windows) or in your Tomcat startup settings (Linux).
  4. Restart the Tomcat service. This briefly interrupts the portal, so schedule it accordingly.
  5. Run the check again and confirm only the "Your keystore contains…" line appears.
  6. Confirm the portal's integrations (billing, payments, e-bills, email) are working.

If Tomcat uses its own truststore (a -Djavax.net.ssl.trustStore setting in Tomcat's Java options), updating Java does not change that file. Run the check on it, using the truststore file in place of <cacerts> and its password. If any line starting with "Owner:" appears, apply the interim fix below to that file, even if Java has already been updated.

If You Can't Update Java Right Away (Interim Fix)

This interim fix is from OpenJDK's guidance (openjdk.org/emudhra). It removes the four root certificates OpenJDK lists. It applies to Java downloaded from a vendor and to a Tomcat truststore. For Java installed from a Linux package, update the packages as described above instead. Run the commands as administrator (Windows) or root (Linux) from the Java bin folder, with the same <cacerts> and <truststore password> as the check. If your Java is Eclipse Temurin, contact Silverblaze Support instead, as Temurin names these certificates differently and the commands below will not remove them.

  1. Back up the file:
    • Windows (PowerShell): Copy-Item "<cacerts>" "<cacerts>.bak"
    • Linux: cp "<cacerts>" "<cacerts>.bak"
  2. Remove the certificates. Ignore any messages saying a certificate does not exist.
    • Windows (PowerShell):
      foreach ($a in "emsignrootcag1 [jdk]","emsignrootcag2 [jdk]","emsigneccrootcag3 [jdk]","comodoaaaca [jdk]") { .\keytool.exe -delete -keystore "<cacerts>" -storepass "<truststore password>" -alias $a }
    • Linux:
      for a in "emsignrootcag1 [jdk]" "emsignrootcag2 [jdk]" "emsigneccrootcag3 [jdk]" "comodoaaaca [jdk]"; do ./keytool -delete -keystore "<cacerts>" -storepass "<truststore password>" -alias "$a"; done
  3. Restart the Tomcat service.
  4. Run the check again and confirm only the "Your keystore contains…" line appears. If a line starting with "Owner:" still appears, the file uses different certificate names; contact Silverblaze Support.
  5. Confirm the portal's integrations (billing, payments, e-bills, email) are working. To undo the fix, restore the .bak file and restart Tomcat.

References

Revision History

Questions

Customers with questions about this bulletin, or who need help with any steps above, can email support@silverblaze.com. We continue to monitor disclosed vulnerabilities and will publish an advisory promptly if any are found to affect Silverblaze products.