US News Pulse Newsroom
Editorial Team
Published : Nov 18, 2026
Online Edition

Java4Shell Flaw Lets Hackers Run Code Without a Password - US News Pulse

Java4Shell Flaw Lets Hackers Run Code Without a Password - US News Pulse

A critical flaw in Java's Base64 decoder, dubbed Java4Shell, lets an unauthenticated attacker run code on a vulnerable server without a password, security researchers disclosed on Monday, November 17, 2026. Oracle shipped fixed versions of Java the same day, and the US cybersecurity agency CISA told organisations to patch immediately.

Key Points

  • Java4Shell, tracked as CVE-2026-114938, is an out-of-bounds write in OpenJDK's hardware-accelerated Base64 decoder, rated 9.2 Critical under CVSS 4.0.
  • An unauthenticated remote attacker can overwrite 62 to 63 bytes of the Java heap and, in the worst case, run code without a password.
  • Researchers demonstrated pre-authentication remote code execution in six major products in default configurations: Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.
  • The flaw affects OpenJDK 17.0.6 and later, plus Java 21, 25 and 27, but only on x86-64 systems with AVX-512 VBMI support; ARM64 runtimes are not affected.
  • Oracle released fixed builds on November 17; CISA urged immediate patching, and no exploitation in the wild has been reported.

What Happened

Security firm Calif disclosed the flaw on Monday, November 17, 2026, after researcher Quang Luong found the bug in about an hour with the help of artificial intelligence. The flaw sits in the part of OpenJDK that decodes Base64 data using AVX-512, specialised instructions on modern Intel and AMD processors. Fed a crafted value, it miscalculates its output space and writes past its destination array.

The trigger is strikingly small: 128 letter A characters followed by a single equals sign. The decoder calculates it needs 98 bytes, then its fast AVX-512 path writes 62 bytes beyond that buffer, corrupting whatever sits next to it in the Java heap. In a Datadog test, the write corrupted a neighbouring array's header and the virtual machine later crashed during garbage collection. Calif also showed a client-side exploit against a Java program connecting to a malicious TLS server.

Background and Context

Java runs much of the enterprise internet. Banks, hospitals, government agencies and large companies rely on it for servers handling logins, payments and internal tools, and many decode Base64 data constantly. Base64 packs binary data into text, and it shows up in authentication tokens, session cookies, security certificates and SAML sign-in messages. A flaw in the decoder itself therefore reaches far beyond any single application.

The name Java4Shell echoes Log4Shell, the 2021 Log4j flaw that sent security teams scrambling. The comparison is limited: Log4Shell could be triggered with a single crafted string in almost any Java application, while Java4Shell needs a specific processor feature and attacker-controlled data reaching the decoder. It lands amid other attacks: our report on the Optimizely supply-chain hack that hit 178 websites, including CNN and the BBC shows how quickly one weakness can spread.

Java4Shell: How the Flaw Works

The bug lives in the final-fragment handler of the AVX-512 Base64 decoder. The decoder converts each 64-byte block of input into 48 bytes of output, and a separate routine handles what is left at the end. That routine divides the remaining length by four, discards the remainder and multiplies by three. For a one-byte fragment that gives zero; subtracting one for a trailing padding character makes it minus one, unchecked.

AVX-512 supports masked stores, where mask bits decide which bytes reach memory. The decoder builds its mask from the output count with the BZHI instruction. For minus one, the count's low byte is 255, beyond the 64-bit operand's width, so all 64 bits stay set and the store writes far more than it should.

Three conditions must all hold: a vulnerable Java version, a processor with AVX-512 VBMI support, and attacker-controlled data reaching the affected decoder. The basic and URL decoders are affected; the MIME decoder is not. Datadog notes denial of service is the more readily achievable impact; reliable code execution needs work tailored to each application.

Reactions and Quotes

Oracle moved fast, shipping fixed builds the same day as part of its November 17 Critical Patch Update, covering Java 17, 21, 25 and 27, and rating the flaw 8.1 under the older CVSS 3.1 system. CISA issued an alert telling organisations to patch immediately.

Datadog Security Labs, which published a detailed technical analysis, urged calm about the worst case while insisting the patching could not wait. "There is no single, universal exploit that would work against all Java applications," its researchers wrote.

Teams that cannot patch at once can buy time with a startup flag: -XX:-UseBASE64Intrinsics disables the vulnerable path, and -XX:UseAVX=2 on x86-64 limits the virtual machine to AVX2. Both need a restart, and the AVX flag must not be used on ARM64 systems, which do not recognise it.

Why It Matters

The six products Calif demonstrated against are not obscure. Keycloak and PingFederate guard logins for countless organisations, Jenkins builds and ships their software, and Jira and Confluence run their daily work. A pre-authentication flaw in any one would be serious; one flaw reaching all six is what earns the 9.2 rating.

The overwrite is constrained rather than freely chosen, which limits what one malformed input can do. But heap corruption is unpredictable: a write into unused space can go unnoticed, while a write into an object header can damage information the virtual machine consults later, including during garbage collection. Catching the exception does not undo the damage.

What Happens Next

The immediate step is patching: update to the fixed builds Oracle released on November 17, 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, and check bundled runtimes and container images, not only the Java installation on the system path. After updating a container base image, rebuild and redeploy the application image and restart affected Java processes.

Teams that cannot patch at once should apply a workaround flag and verify it took effect with jcmd, and check whether their processors support AVX-512 VBMI at all. Attention now turns to the vendors of the six demonstrated products. Calif has not released its exploits, but the history of major Java flaws suggests that window will not stay open long. Our report on the NSA Net outage is a reminder of how much infrastructure depends on systems rarely seen until they fail.

Frequently Asked Questions

What is Java4Shell?
Java4Shell is the nickname for CVE-2026-114938, a flaw in OpenJDK's Base64 decoder. A malformed value can make it write past its buffer, letting an unauthenticated attacker run code without a password in the worst case.

Which Java versions are affected?
OpenJDK 17.0.6 and later, plus Java 21, 25 and 27. The fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, released by Oracle on November 17, 2026.

Am I affected on ARM?
No. The flaw only runs on x86-64 processors with AVX-512 VBMI support, such as Intel Ice Lake or later and AMD Zen 4 or later. ARM64 runtimes are not affected.

How do I fix Java4Shell?
Update to the fixed Java build for your version line and restart affected processes, including bundled runtimes and container images. If you cannot patch at once, use -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 on x86-64 only.

Has Java4Shell been exploited in the wild?
No. Calif demonstrated exploits against six products but has not released them, and Datadog notes there is no single universal exploit for all Java applications.

US News Pulse
Written by
US News Pulse Newsroom
Editorial Team

The US News Pulse newsroom covers breaking news across the United States and the world, working from wire services, official statements and on-the-record sources. Every story is reviewed against our editorial standards before publication. Corrections and tips: info@usnewspulse.com

About our newsroom

Leave a Comment

  • Latest
  • Popular

Ciro Tomlian Charged After Cane Attack on Turning Point USA

1

Jessica Pegula salva un punto de partido y vence a Noskova p

2

Drones Golpean Tres Buques Cerca del Canal de Sulina en Agua

3

Senate Democrats Order Musk to Preserve Starlink and Starshi

4

Decisión sobre el nuevo juicio de Lindsay Clancy este lunes

5

Matt Boldy Hat Trick Powers Wild Past Leafs 5-2 in NHL Thurs

6

La Casa Blanca retira a Heidi Overton, nominada para dirigir

7

Tormenta invernal en California deja hasta 61 cm de nieve y

8

Bukele's Troops Retake Haiti's Sylvio Cator Stadium From Gan

9

Home Depot Names Finance Chief Richard McPhail as CEO as Q3

10

Kucherov logra triplete y Tampa Bay golea 8-3 a Buffalo; Car

11

Alex Murdaugh pide anular las acusaciones de asesinato por e

12

Trump reduce el recorte de tropas en Europa a 5.000 y alivia

13

Baréin activa las sirenas de alerta y ordena refugiarse mien

14

Michael Wilson, de los Cardinals, fuera de temporada tras ju

15

Trump y Netanyahu en una 'pelea a gritos infernal' por Irán,

16

US Postal Service Warns of Deep Post Office Cuts Without Con

17

Leukemia Vaccine Passes Key Phase 3 Trial, Cutting Death Ris

18

Migrante deportado dos veces acusado de amenaza de bomba en

19

Tesla Cybercab Goes on Sale at $29,990 — But It Won't Drive

20