Vulnerability

Critical vulnerability in Java (Java4Shell)

On 17 November 2026, Oracle and the OpenJDK project released an update for a critical vulnerability in Java, known as Java4Shell (CVE-2026-114938). This vulnerability allows an attacker to read memory and execute code in Java applications that process external Base64 input, without the need for login credentials. There are currently no known instances of this being exploited in the wild. The researchers have published technical details and a limited proof-of-concept.

Clip path group@2x

T-Update

Information about vulnerabilities

This live blog contains information regarding a critical vulnerability in Java (Java4Shell).

Latest blog update on 18 November
‍

Update 18 November 2026

Oracle and OpenJDK released updates for Java4Shell on 17 November at 22:00 CET. Research firm Calif demonstrated unauthenticated code execution in default installations of Atlassian Jira and Confluence, Jenkins, and Keycloak, among others. No exploitation has been observed yet. Updates for Ubuntu, Debian, and Red Hat Enterprise Linux are not yet available. On 17 November, the NCSC published advisory NCSC-2026-0495 regarding vulnerabilities in Oracle Java, with a classification of medium/high (likelihood/impact). We advise patching immediately where possible, or applying the temporary mitigation.

‍

‍

Tailored cybersecurity

Background

Java is the runtime platform underpinning a large proportion of enterprise applications, such as Atlassian Jira and Confluence, Jenkins, Keycloak, Elasticsearch, and applications built on Spring Boot and Apache Struts. Many of these products include their own Java runtime. The vulnerability lies in an optimised Base64 decoder within the HotSpot JVM. On processors with AVX-512 VBMI, Java uses a faster routine. When presented with invalid input, this routine writes 62 to 63 bytes beyond the end of the buffer before Java rejects the input. Base64 is widely used in login flows, uploads, and network messages.

Risk

There is currently no known exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalogue. According to Cyber Security News, CISA is urging organisations to patch immediately.

Calif has published a technical description and a limited proof-of-concept. This demonstrates whether a Java version and processor are vulnerable, but does not provide code execution. Calif is withholding product-specific exploits with plans to publish them later.

Calif reports the following results in standard configurations:

  • Without authentication: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.
  • With authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
  • Example applications on Apache Struts and Spring Boot.
  • Client-side: a Java program that opens a TLS connection to a malicious server.

In addition to code execution, an attacker can read memory, similar to Heartbleed. This can lead to the leakage of session tokens and private keys. A failed attempt may cause the application to crash.

Vulnerable versions include OpenJDK 17 from 17.0.6, 21, 25 and 27, and distributions based on these, such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat build of OpenJDK, Oracle Java SE and Oracle GraalVM. Oracle also mentions Java SE 8u511b33-perf (Enterprise Performance Pack). Standard Java 8 and Java 11 are not considered vulnerable according to available analyses.

The vulnerability is only exploitable on x86-64 processors with AVX-512 VBMI. These include Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, as well as AMD processors from Zen 4 onwards. ARM64 is not vulnerable. These are widely used server processors, including in cloud environments.

‍

Advice

Install the patched Java version and restart all Java processes.

Release line - Patched version (Oracle)

Java 27 - 27.0.1.1

Java 25 - 25.0.5.1

Java 21 - 21.0.13.1

Java 17 - 17.0.21.1

Java 8 Enterprise Performance Pack - 8u513-perf


Amazon Corretto 17.0.21.1.2 contains the fix. For other distributions, follow the vendor's advice. As of 18 November, there were no updates yet for Ubuntu, Debian, Rocky Linux, AlmaLinux, and RHEL. Red Hat states in bulletin RHSB-2026-018 that the fixes are being released as a priority.

If you cannot patch yet, start the JVM with -XX:-UseBASE64Intrinsics. This disables the vulnerable routine, potentially with some loss of performance. The alternative is -XX:UseAVX=2, which has a greater performance impact. Use this latter option only on x86-64: the option does not work for a JVM on ARM.
Restart the process after adding the option. A reverse proxy or request buffering in nginx is not a reliable mitigation.

Patching does not undo any previous compromise. Investigate systems that were accessible from the internet while unpatched for signs of abuse.

Additional measures

  1. Inventory all Java runtimes, including runtimes bundled with products (such as Jira and Confluence), container images, and appliances.
  2. Check whether the processor supports AVX-512 VBMI. On Linux, the flags avx512f, avx512bw, avx512vbmi, and bmi2 must be present in /proc/cpuinfo.
  3. Prioritise applications accessible from the internet, such as Jira, Confluence, Jenkins, Keycloak, and PingFederate.
  4. After patching, check which Java version the running process is using, rather than just the default installation on the host. Check the active options with jcmd <PID> VM.flags -all.
  5. Rebuild container images with a patched runtime.
  6. Monitor for unexpected JVM crashes (hs_err_pid files), suspicious processes launched from Java, and unknown Java runtimes. A crash on an unpatched, accessible system warrants investigation.

‍
Do you have questions about the possible impact on your environment or do you need support? Contact T-CERT, available 24/7, for an impact analysis or support. Subscribe to T-Updates to stay informed.

Ellipse 6

Sign up for T-Updates

Receive the latest news about malware or vulnerabilities in your inbox every Wednesday

More than 1,000 organizations have already joined us.

Tesorion uses your data to send the requested information. In addition, your data may be used for commercial follow-up. You can unsubscribe from this at any time via the link in the email. For more information, read our privacy policy.

Ellipse 6