Independent reporting on data, AI and digital regulation in Luxembourg

Finance & DORA · News

Java4Shell: CSSF and CIRCL urge Luxembourg firms to patch Java flaw CVE-2026-114938

On 18 November 2026 the CSSF and CIRCL warned Luxembourg organisations about Java4Shell, CVE-2026-114938, a critical flaw in the Java runtime's Base64 decoder.

Key takeaways

  • On 18 November 2026 the CSSF asked all supervised entities concerned to act on Java4Shell, CVE-2026-114938, a critical flaw in the OpenJDK Base64 decoder, and pointed to CIRCL report TR-104.
  • The CSSF states that unauthenticated remote code execution through the flaw is unauthorised malicious access and a major ICT-related incident, to be notified under Circular CSSF 25/893 (DORA) or 24/847, depending on the entity.
  • OpenJDK and Oracle released fixes on 17 November 2026; CIRCL lists Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 as the fixed upstream versions.
  • According to CIRCL, the flaw is only reachable on x86-64 processors with AVX-512 VBMI, such as Intel Xeon Ice Lake or AMD Zen 4 and later, when attacker-controlled Base64 data reaches the decoder.
  • As of 18 November 2026 CIRCL had not confirmed widespread exploitation in the wild; a public local proof of concept exists.

Luxembourg’s financial supervisor and its national CERT want organisations running Java to patch now. On 18 November 2026 the CSSF warned supervised entities about Java4Shell, CVE-2026-114938, a critical memory-corruption flaw in the OpenJDK Base64 decoder, and CIRCL published report TR-104 with fixed versions and mitigations. OpenJDK and Oracle released the fixes on 17 November.

What happened

The flaw is a heap-based out-of-bounds write in the hardware-accelerated Base64 decoder of the HotSpot Java virtual machine on x86-64. Specially crafted Base64 input can corrupt memory and, depending on the application, lead to information disclosure, a crash or unauthenticated remote code execution. Oracle rates it 8.1 under CVSS v3.1; Calif, the researchers who reported it, rate it 9.2 under CVSS v4.0. The US agency CISA called for immediate patching on 17 November.

The CSSF adds the regulatory consequence. Unauthenticated remote code execution through this flaw is unauthorised malicious access, and that constitutes a major ICT-related incident to be notified under Circular CSSF 25/893 or 24/847, depending on the type of entity. Since 28 May 2025, 25/893 covers DORA entities and payment service providers outside DORA; 24/847 applies to the other entities.

Release line Fixed upstream version (CIRCL TR-104)
Java 17 17.0.21.1
Java 21 21.0.13.1
Java 25 25.0.5.1
Java 27 27.0.1.1
Oracle Java 8 Enterprise Performance Pack 8u513-perf

CIRCL, citing Red Hat, says standard OpenJDK 8 and 11 do not contain this vulnerable code. Oracle also lists affected builds of GraalVM for JDK and GraalVM Enterprise Edition.

Who is actually exposed

Not every Java server is at risk. According to CIRCL, all four conditions must hold: an unpatched JVM, an x86-64 processor with AVX-512 VBMI (for example Intel Xeon Ice Lake or AMD Zen 4 and later), the Base64 intrinsic enabled, and attacker-controlled data reaching the decoder. ARM64 machines are not affected.

The research team reported pre-authentication exploit demonstrations in default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. CIRCL stresses that this does not prove every installation is exploitable, and as of 18 November it had not confirmed widespread exploitation in the wild.

Why it matters

Do you know which Java runtime your identity provider, your CI server and your vendor’s appliance actually use? Probably not by heart. Java is often bundled inside products, so the system’s java command may not be the one serving requests. CIRCL is blunt on this point: updating application libraries does not fix a bundled vulnerable JVM.

An inventory that stops at the operating system is not an inventory.

The good news: the exposure conditions are narrow, the fixes exist for every supported line, and a one-flag mitigation buys time. The work is mostly finding the runtimes, then restarting them.

What to do now

  1. List every Java process, including runtimes bundled in vendor products and container images. CIRCL recommends jcmd -l and jcmd <PID> VM.command_line to see the real JVM.
  2. Prioritise Internet-facing authentication services, CI/CD servers and APIs that handle untrusted Base64, and patch them to the fixed builds. Restart every Java process and rebuild containers.
  3. If you cannot patch at once, start the JVM with -XX:-UseBASE64Intrinsics, check the flag with jcmd <PID> VM.flags -all, and record the residual risk. A web application firewall is not a general fix.
  4. Watch for unexpected JVM crashes, unusual child processes and outbound connections. Do not run public exploits against production systems.
  5. If you are CSSF-supervised, prepare now for the notification under Circular 25/893 or 24/847, so that a confirmed compromise does not start with a search for the right form and the right person. If personal data may be affected, the GDPR steps described for the PHP flaws of October 2026 apply in the same way.

Questions & answers

Which Java versions fix CVE-2026-114938?

According to CIRCL report TR-104, the fixed upstream versions are Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and 8u513-perf for the Oracle Java 8 Enterprise Performance Pack. Vendors such as Amazon Corretto, Azul and Red Hat publish their own build numbers.

Is Java 8 or Java 11 affected by Java4Shell?

CIRCL, citing Red Hat, says standard OpenJDK 8 and 11 are not affected by this specific flaw, although other November 2026 security fixes still apply. The Oracle Java 8 Enterprise Performance Pack build 8u511b33-perf is affected.

Must a CSSF-supervised entity report Java4Shell to the CSSF?

The vulnerability alone is not an incident. The CSSF says that unauthenticated remote code execution through it constitutes a major ICT-related incident, to be notified under Circular CSSF 25/893 for DORA entities or Circular CSSF 24/847 for the other entities it covers.

Is there a workaround if Java cannot be patched at once?

CIRCL names the JVM option -XX:-UseBASE64Intrinsics as the generally preferred temporary mitigation, with -XX:UseAVX=2 as a broader alternative. Neither removes the vulnerable code, and both must be checked on the JVM that actually runs the service.

Sources

  1. Critical Memory Corruption Vulnerability in OpenJDK Base64 Decoder (Java4Shell) (18 November 2026) · CSSF
  2. TR-104 – Critical Memory Corruption in OpenJDK Base64 Decoder (Java4Shell, CVE-2026-114938) · CIRCL
  3. CVE-2026-114938 · CIRCL Vulnerability-Lookup
  4. Critical Java vulnerability requires immediate patching (17 November 2026) · CISA
  5. Publication of two new circulars: ICT-related incident classification and reporting for DORA entities and other payment service providers (28 May 2025) · CSSF

Written and fact-checked against primary sources.