Threat Intelligence

Java4Shell: A Java Base64 Flaw Puts Jira, Jenkins and Keycloak at Risk on Some Servers

The Hacker News · 18 Nov 2026
Key Takeaway Check which of your Java servers run version 17 or later on AVX-512 VBMI capable chips and apply the fixed Java releases as soon as your vendor provides them.

Security firm Calif has disclosed a Java vulnerability called Java4Shell (CVE-2026-114938) that could let attackers without an account run their own code on applications including Jira, Jenkins and Keycloak. Oracle and the OpenJDK project released fixes this week. Amazon has fixed its Corretto builds, while Red Hat is still preparing its own.

The flaw sits in a faster Base64 decoder that Java uses on x86-64 Intel and AMD chips with the AVX-512 VBMI feature, after the code has run often enough to be compiled for speed. A malformed string ending in an extra = makes the decoder write 62 or 63 bytes past the end of its output before Java rejects the string. Servers often decode Base64 data, such as HTTP Basic login headers, SAML artifacts and CSRF tokens, before checking who is logged in, which is how an attacker needs no account.

Affected versions include Java 17.0.6 and later on the 17 line, plus Java 21, 25 and 27. Standard Java 8 and 11 are not affected, but the Java SE 8 Performance Pack build 8u511b33-perf and certain GraalVM releases are. Intel Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids chips, and AMD Zen 4 or newer, can run the vulnerable code. ARM64 chips do not.

Real-world risk is still unclear. Calif is withholding its attack code, and other labs have reproduced crashes and a memory leak but not code execution. Each target needs its own memory layout and timing, and failed attempts can crash Java. Canada's Cyber Centre knows of no attacks, and the flaw was not in CISA's KEV catalog when checked. Severity scores vary, from 8.1 (Oracle) to 9.8 (Red Hat, preliminary).

Why it matters

Pre-authentication paths such as login headers and tokens mean a login screen and access controls do not protect exposed Java services, since the bug triggers before identity is checked. Because the vulnerable code runs only on certain chips, the same container image can be exposed on one host and safe on another, so version inventories alone will misjudge risk. Even without proven code execution, repeatable crashes make availability of identity and build systems a real concern.

What to do

  • Update Java to the fixed .1 releases, such as 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, for Oracle builds.
  • Check each Linux server's CPU for avx512f, avx512bw, avx512vbmi and bmi2 flags to find where the vulnerable code can run.
  • Review Java 17+, Java SE 8 Performance Pack 8u511b33-perf and affected GraalVM builds across Jira, Jenkins, Keycloak and similar systems.
  • Watch for repeated Java crashes and bursts of malformed login requests against exposed services.
Java CVE-2026-114938 Java4Shell RCE Patch Management

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.