Thursday, November 19, 2026 Latest IEA Chief Calls Strait Crisis ‘Greatest Threat’ Ever Our standards
Business

Researcher Quang Luong Finds Critical Java4Shell Flaw in Three Hours

A critical memory safety flaw in the world's third-largest programming language lets unauthenticated attackers run code remotely on enterprise servers, prompting international patches and government warnings.

Stock photo shows working professional at computer desk with screens showing Java code in an office environment
Stock photo shows working professional at computer desk with screens showing Java code in an office environment

A critical memory safety flaw in the world’s third-largest programming language lets unauthenticated attackers run code remotely on enterprise servers, prompting international patches and government warnings.

Java4Shell Flaw Exposes Core Infrastructure

The flaw involves code that writes data to incorrect memory locations. This can crash a program or allow an attacker to run their own commands.

This weakness exists only on AMD and Intel x86-64 processors with AVX-512 VBMI support. California researcher Quang Luong found the bug while checking OpenJDK HotSpot with an AI coding tool.

Java4Shell RCE Demos: Keycloak, Jira, Confluence, Kafka, Elasticsearch, etc.

The firm said the process took about three hours and cost less than $200 in tokens. Professor Toby Walsh said the incident is a serious flaw in a language built to protect memory. He said the bug had been “hiding in plain sight for 12 years.”

Versions and Technical Scope

The flaw affects OpenJDK 17.0.6 and later versions. This includes distributions from Oracle, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat.

Oracle Java SE builds identified as vulnerable are 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, and 27.0.1.0.3. Updated builds from Oracle are 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.

Amazon released updated Corretto builds on November 17, such as 17.0.21.1.2 and 21.0.13.1.2. For Oracle Java SE 8, the Enterprise Performance Pack build 8u511b33-perf is vulnerable, while 8u513-perf is the patched version.

Vendors ship OpenJDK packages on different schedules. Organizations must confirm their specific distribution’s version labels.

Calif Rates Flaw 9.2 Critical While Oracle Assigns 8.1

Industry groups assign different severity levels to the flaw. Calif rates Java4Shell as a 9.2 under CVSS 4.0, classifying it as “Critical.”

Researcher Quang Luong Finds Critical Java4Shell Flaw in Three Hours
Photo: Endor Labs

Oracle’s advisory is part of its November 17 Critical Security Patch Update, which addressed 11 Java SE vulnerabilities. It assigns a CVSS 3.1 score of 8.1. Oracle said the flaw is remotely exploitable without authentication, though it has high attack complexity.

Calif demonstrated that an attacker using “heap grooming” can achieve remote code execution. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) urged organizations to patch immediately. No exploitation in the wild had been reported as of publication.

South Korea Issues Urgent Advisory as Java Runs 90% of Fortune 500

Java runs at 90% of Fortune 500 companies. In South Korea, the government issued an urgent advisory because 89.1% of central administrative agencies’ information systems rely on the language, which is used for 53% of programming tasks there.

Calif recommends two temporary mitigations for organizations unable to patch immediately. Start the Java application with the flag -XX:-UseBASE64Intrinsics to disable the vulnerable decoder. Use -XX:UseAVX=2 to prevent the JVM from using AVX-512 instructions.

Administrators should audit their environment for internet-exposed services. They must verify if their CPU hardware supports the vulnerable AVX-512 VBMI feature set before prioritizing remediation efforts.

Accuracy matters. See something that needs attention? Read our corrections policy or contact the newsroom.

Business Editor

Marcus Lin

Marcus Lin leads TellingPointy's Business desk, covering companies, markets, labor, trade, regulation, and the economics of everyday life. He examines balance-sheet realities, competitive pressure, and the effects corporate decisions have on workers and consumers.