CriticalTLP:CLEARGARNET-CSIRT-2026-012

Java (OpenJDK) Base64 Remote Code Execution Vulnerability (Java4Shell)

Oracle and the OpenJDK project have fixed CVE-2026-114938, known as Java4Shell, a memory corruption flaw in the JVM's Base64 decoder on modern x86-64 servers. Crafted input from an unauthenticated user can crash a Java service, and the researchers who found it achieved remote code execution against several popular Java applications. Update Java 17, 21, 25 and 27 runtimes, including the Amazon Corretto runtimes most member institutions use for their Shibboleth Identity Providers.

Summary

On 17 November 2026 Oracle and the OpenJDK project fixed CVE-2026-114938, a memory corruption flaw in the Java Virtual Machine that its finders at Calif named Java4Shell. CISA has urged organisations to patch immediately.

The bug is in the optimised Base64 decoder Java uses on x86-64 processors with AVX-512 VBMI. Crafted input makes it write past the end of its buffer before Java rejects the input, so any Java service that decodes untrusted Base64 with java.util.Base64 can be reached. ARM64 servers and older x86-64 processors are not affected.

Impact

Exploitability signals: CVSS 3.1 8.1 (Oracle) and CVSS 4.0 9.2 · unauthenticated, network reachable · remote code execution demonstrated · no exploitation in the wild reported as of 18 November 2026 · not on the CISA KEV catalog.

Crashing an affected service is easy. A short burst of crafted requests is enough. Remote code execution is harder and needs an exploit tailored to each application, but Calif achieved it without login against Keycloak, PingFederate, Jira, Confluence, Artifactory and Jenkins. No general exploit is public yet, though researchers built a working proof of concept within hours of disclosure.

A compromised Java service gives the attacker everything the process can reach, including database credentials, session secrets and signing keys.

Affected systems

A system is vulnerable only if it runs an affected Java runtime and its CPU supports AVX-512 VBMI (Intel Xeon Ice Lake or newer, AMD Zen 4 or newer, including many cloud instances).

  • Java 17 from 17.0.6, fixed in 17.0.21.1 (Corretto 17.0.21.1.2)
  • Java 21 fixed in 21.0.13.1 (Corretto 21.0.13.1.2)
  • Java 25 fixed in 25.0.5.1 (Corretto 25.0.5.1.2)
  • Java 27 fixed in 27.0.1.1 (Corretto 27.0.1.1.4)

Oracle Java SE 8 Performance Edition and Oracle GraalVM are also affected and fixed in the same release. Standard Java 8 and 11 are not affected. Other distributions (Temurin, Zulu, Red Hat, Microsoft and others) are shipping November 2026 builds; check your vendor’s release notes.

To check a Linux host’s CPU, run the command below. The host is affected only if all four flags are printed.

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

Shibboleth Identity Providers

Most member institutions run a Shibboleth IdP on Amazon Corretto. IdP v5 requires Java 17 or later, so assume your IdP is on an affected runtime unless Corretto was updated on or after 17 November.

Shibboleth decodes SAML messages with its own library rather than Java’s built-in decoder, so ordinary SAML logins are not known to reach the flaw. Its servlet container (Jetty or Tomcat) and some plugins do use the vulnerable decoder, however, and the Shibboleth project has not yet published an assessment. Patch the IdP anyway: it holds the keys that sign every login, and an attacker with them can sign in as any of your users to every federated service, including eduroam.

To check, find the Java the running IdP uses (not the default java on the path) and confirm it reports Corretto-17.0.21.1.2 or Corretto-21.0.13.1.2 or later:

$(ps -o args= -C java | grep -o -E '^[^ ]+' | head -1) -version

To update, upgrade the java-17-amazon-corretto or java-21-amazon-corretto package (or install the new Corretto archive or Windows MSI), restart Jetty, and sign in once to confirm login still works.

Temporary mitigations

Only where you cannot update straight away:

  • Add -XX:-UseBASE64Intrinsics to the JVM options (for a Shibboleth IdP, Jetty’s JAVA_OPTIONS) and restart. This turns off only the vulnerable decoder.
  • Restrict Java services that do not need to be public to the campus network or VPN.

A web application firewall will not block every path to the decoder.

Action

  1. Find every Java runtime, including those bundled in applications, appliances and container images. Common ones in our community: Shibboleth IdP, Keycloak, CAS, DSpace, Dataverse, Solr, Elasticsearch and OpenSearch, Tomcat applications, Jenkins, Jira and Confluence.

  2. Update Java now. Start with services that have a proven attack path (Keycloak, CAS, Jira, Confluence, Jenkins), then your Shibboleth IdP, then everything else, internet facing first.

  3. Restart and verify. Running JVMs keep the vulnerable code until restarted. Rebuild container images on patched base images and confirm each running process reports the fixed version.

  4. Watch for signs of attack: unexpected JVM crashes, new hs_err_pid*.log files, and Java processes starting shells or making unusual outbound connections.

  5. If you suspect compromise, rotate every secret the JVM held. For a Shibboleth IdP this means its signing and encryption keys (with a federation metadata update) and its LDAP or Active Directory account. Report the incident so we can correlate activity across the constituency.

  6. Do not run proof-of-concept code from unknown sources. Fake exploit repositories often contain malware.

Verify this advisory✓ PGP-signed

This advisory is published with a detached PGP signature against the CSIRT key. Confirm it is genuine and unmodified before acting:

$ curl -O https://csirt.garnet.edu.gh/advisories/2026-012-java-openjdk-base64-remote-code-execution-vulnerability-java4s.md
$ curl -O https://csirt.garnet.edu.gh/advisories/2026-012-java-openjdk-base64-remote-code-execution-vulnerability-java4s.md.asc
$ gpg --import garnet-csirt.asc
$ gpg --verify 2026-012-java-openjdk-base64-remote-code-execution-vulnerability-java4s.md.asc 2026-012-java-openjdk-base64-remote-code-execution-vulnerability-java4s.md

Downloads: source .md · signature .md.asc · public key. Check the fingerprint (684C7B7DA77E4F1B68AED3ECE84B541C6184CC6F) on the PGP page — if gpg reports a “Good signature” from that key, this advisory is authentic.


Think a system in the community is affected or compromised?Report an incident