Java4Shell vulnerabilities: What you need to know

Java4shell

A critical security vulnerability has been discovered in Java runtimes, including OpenJDK and Oracle Java, which are widely used to power enterprise applications and services. The vulnerability, identified as CVE-2026-114938 and nicknamed Java4Shell, could allow an unauthenticated attacker to remotely execute arbitrary code, access sensitive information, or crash an application on affected systems.

The vulnerability has received a CVSS v4.0 severity score of 9.2 out of 10 (Critical) from the researchers at Calif who discovered it, and a CVSS v3/1 score of 8.1 (High) from Oracle and OpenJDK.

On November 17, Oracle released emergency security updates addressing the vulnerability. A proof-of-concept exploit is publicly available, and researchers have demonstrated working remote code execution exploits. As of November 18, there are no confirmed reports of exploitation in the wild. Learn more about Java4Shell.

What is DigiCert doing to protect its systems?

DigiCert has assessed the impact and applied a Java runtime flag to mitigate the vulnerability in affected products and services. DigiCert will apply the official patch as soon as it becomes publicly available.

WAF is also blocking Java RCE exploitation attempts, providing an additional layer of protection for major DigiCert products. This protection does not replace patching.

Please check back in 24 hours for the latest status update. Thank you for your patience as our team works to complete the process.

Affected DigiCert products and services:

Confirmed unaffected products and services:

What is Java4Shell?

Java4Shell refers to a remote code execution (RCE) vulnerability in Java’s built-in Base64 decoder (java.util.Base64.Decoder). On affected systems, specially crafted Base64 input can cause memory corruption, which could allow an attacker to execute arbitrary code, access sensitive information, or crash the application.

Applications that process untrusted Base64 data, such as authentication headers, tokens, or encoded request parameters, may be vulnerable. Authentication is not required if the vulnerable decoder can be reached before authentication takes place.

Not every application running an affected Java version is necessarily exploitable. Exploitation requires all of the following:

Which Java versions are affected?

Distribution / version
Affected versions
Fixed version
OpenJDK/ Oracle Java 17
17.0.6 through vulnerable 17.0.21 builds
17.0.21.1
OpenJDK / Oracle Java 21
Unpatched 21.x builds through 21.0.13
21.0.13.1
OpenJDK / Oracle Java 25
Unpatched 25.x builds through 25.0.5
25.0.5.1
OpenJDK / Oracle Java 27
Unpatched 27.x builds through 27.0.1
27.0.1.1
Oracle Java 8 Performance Pack
8u511b33-perf
8u513-perf
Oracle GraalVM
Affected Java 17 and 21 builds
See Oracle advisory
Amazon Corretto 17 / 21 / 25 / 27
Affected builds
17.0.21.1.2 / 21.0.13.1.2 / 25.0.5.1.2 / 27.0.1.1.4

Other distributions, including Eclipse Temurin, Azul Zulu, Red Hat OpenJDK, and Microsoft OpenJDK, may also be affected. Refer to your vendor’s security advisory, since affected builds and fixes vary and patch versions are distribution-specific.

Java 18 and other end-of-life versions (19–20, 22–24, and 26) may be affected and no longer receive security updates. Organizations running them should upgrade to a supported, patched release. Standard OpenJDK builds of Java 8 and 11 are not generally reported as affected, with the Oracle Java 8 Performance Pack as a documented exception.

What do you need to do?

Organizations that independently operate Java-based applications should check whether they are affected and apply the appropriate update, regardless of whether they use DigiCert products. Upgrade to a patched release (when ready) and restart the relevant services so the updated runtime is in use. After remediation, verify the deployed Java version.

If you cannot patch immediately, the researchers who discovered the vulnerability recommend two temporary workarounds, which are also documented in Red Hat’s security bulletin. Oracle has not published an official workaround and states that the fix is to upgrade.

These are temporary measures, not permanent fixes. Apply a patched Java runtime as soon as possible.

Staying informed

DigiCert continues to monitor security developments that could affect our products, services, and customers.

For the latest technical details and available patches, see the OpenJDK security advisory and the Oracle Java security advisory.