Technology

Home  •  Blog  •  Java4Shell: A 65-Character Strin...

Java4Shell: A 65-Character String Can Break Java, and the Patch Race Is On

A critical bug in OpenJDK's accelerated Base64 decoder lets researchers hijack Jira, Jenkins and Keycloak in tests, but exploitation is harder than Log4Shell

A coffee cup patterned with glowing circuit lines splits along a red crack in a dark server room, glowing data spilling from the fracture

A single malformed string of 64 letters and an equals sign can corrupt memory inside Java, and security teams worldwide are now racing to patch the runtime that quietly powers banks, airlines and enterprise IT.

A newly disclosed flaw nicknamed Java4Shell has put one of the world's most widely used software platforms on an urgent patch footing. Tracked as CVE-2026-114938, the bug sits in the Base64 decoder of OpenJDK, the open-source foundation of most Java runtimes, and was disclosed on Tuesday, Nov. 17, by security research firm Calif. OpenJDK published an advisory and Oracle shipped fixed builds the same day at 1:00 p.m. Pacific time, according to Calif, which rates the flaw 9.2 out of 10, or Critical, under the CVSS 4.0 scoring system.

The headline risk is stark: researchers say a remote attacker with no login can, under the right conditions, overwrite heap memory, leak its contents in the style of the 2014 Heartbleed bug, and ultimately run their own code. But several independent analyses stress that real-world exploitation is far harder than the name suggests, and no attacks in the wild had been reported at the time of writing.

What exactly is broken

Base64 is a routine way of turning binary data into text, and it is everywhere: login headers, web tokens, cookies, file uploads and network messages. To decode it faster, OpenJDK uses hand-written assembly code that taps AVX-512 VBMI instructions on modern Intel and AMD server chips. Calif says the bug lives in the part of that code that handles the last few characters of an input. Feed the decoder 64 'A' characters followed by a single '=', and the routine miscalculates a negative output length, then performs a full 64-byte write that spills 62 bytes past the end of a 50-byte array. Java eventually rejects the input, but by then neighbouring objects in memory may already be damaged.

That is notable because memory safety is one of Java's core selling points. The vulnerable code is not Java itself but low-level assembly underneath it, where this class of bug is still common. Datadog Security Labs describes the issue as an out-of-bounds write and says that in its own testing the corruption damaged a neighbouring array's header and later crashed the JVM during garbage collection.

Which apps and systems are exposed

Calif says it achieved remote code execution without authentication against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and with a login against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It calls those lists non-exhaustive and says it also demonstrated attacks on sample apps built with Apache Struts and Spring Boot. A separate client-side exploit, shared with Calif by researcher samczsun, reportedly compromises a Java program simply by having it open a TLS connection to a malicious server, as BleepingComputer reported.

The flaw affects OpenJDK from version 17.0.6 onward, along with distributions built on it, including Amazon Corretto, Eclipse Temurin, Microsoft's OpenJDK build, Azul Zulu, Red Hat OpenJDK, SAP SapMachine and Oracle's own Java SE and GraalVM. Crucially, it only bites on x86-64 processors that support AVX-512 VBMI, which Calif lists as Intel Xeon chips from Ice Lake onward and AMD processors from Zen 4 onward. ARM64 systems are not affected.

ADVERTISEMENT

How serious is it, really?

Not everyone agrees on the severity number. While Calif scores it 9.2, the EU's cybersecurity service CERT-EU lists a CVSS score of 8.1 and calls it high severity, noting that exploitation requires a vulnerable CPU, the accelerated decoder being active (the default on supported chips) and attacker-controlled Base64 reaching the decoder through channels such as HTTP Basic authentication, JWTs, SAML messages or cookies.

Datadog says denial of service, essentially crashing a Java process, is the more readily achievable impact, while reliable code execution needs extra work tailored to each application and JVM environment. There is no single universal exploit. Palo Alto Networks draws the comparison directly, saying the bug warrants prompt, prioritised patching but is "not another Log4Shell," the 2021 logging flaw that was trivially exploitable across the internet. Canada's Canadian Centre for Cyber Security says it is not aware of active exploitation but warns that can change quickly, and Cloudflare says it has seen no sign of exploitation on its own infrastructure.

The fixes and stopgaps

Fixed Oracle builds include Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, plus a Java 8 performance-pack update, according to the Canadian advisory. BleepingComputer notes the fix arrived as part of Oracle's November Critical Security Patch Update, which covers 655 vulnerabilities across Oracle's portfolio. Agencies advise organisations to inventory every Java runtime, including copies bundled inside third-party products and container images, prioritise internet-facing systems, and restart every JVM after updating.

Where patching has to wait, two startup flags block the vulnerable path: -XX:-UseBASE64Intrinsics, which switches off only the accelerated Base64 routine, or -XX:UseAVX=2, which disables AVX-512 more broadly at some performance cost and must not be used on ARM hosts. The Keycloak project says the first option is Red Hat's preferred interim mitigation and that its 26.8 container images have already been rebuilt on a patched OpenJDK 21.0.13.1.

Why it matters and what to watch

Java runs deep inside banking, telecom, aviation and government systems, so even a bug with narrow hardware requirements touches a vast installed base, and the affected Intel and AMD server chips are exactly the ones that fill modern data centres. The practical challenge for IT teams is less the headline fix than finding every hidden Java runtime tucked inside appliances, vendor software and containers.

Key things to watch in the coming days include whether working exploit code becomes public, whether the flaw is added to the US CISA Known Exploited Vulnerabilities catalogue, and how quickly vendors such as Atlassian, Jenkins and JFrog push updated bundles. For now, the message from researchers and agencies alike is the same: patch Java, then restart it.

Verified Sources & References
TAGS: #Java4Shell #Cybersecurity #Java #OpenJDK #Oracle #Vulnerability
SHARE THIS STORY
Entro

Entro

Staff Writer & Senior Contributor

Curating in-depth stories, analysis, and ideas for Enterteno readers. Committed to editorial accuracy, independent reporting, and original perspective.