Skip to content
Theme
OnDevice Tools

CybersecurityVulnerabilities & Patches

Java4Shell vulnerability puts Java services and devices at risk

Tom's Hardware reports that a critical Java flaw named Java4Shell can allow remote code execution in many Java-based services and devices. Oracle has issued fixes, but a wide range of products and containers may still be affected.

Java4Shell vulnerability illustration showing server racks and a warning message

Key takeaways

  • Java4Shell is a critical OpenJDK flaw rated 9.2 using CVSS 4.0 by Calif Research.
  • The bug can allow remote code execution, including without login in some products.
  • It affects Java-based apps, containers and devices that bundle Java.
  • Oracle has issued fixes, but many vendors must release updates.
In this article
  1. What happened
  2. How the bug works
  3. Which systems are affected
  4. What to do next

What happened

According to Tom's Hardware, the Java4Shell vulnerability is a critical Java flaw. It can let attackers run code on affected systems. The report was published on 19 November 2026.

The flaw was named Java4Shell by the research lab Calif Research. The lab gave it a severity score of 9.2 using CVSS 4.0. CVSS is a common rating system for security flaws. Other vendors have issued their own scores, mostly between 8 and 9.8.

Tom's Hardware says the root cause is in OpenJDK. OpenJDK is the base code that many Java distributions use, including Oracle's. Because Java is widely deployed, the report says the number of exposed sites, services and devices could be very large. The report also says an attacker can trigger the flaw by supplying repeated text.

How the bug works

Illustration: bug, server, privacy, storage and the labels Java4shell, Java, Oracle

The flaw sits in an optimisation for Base64 decoding. Base64 is a way to turn binary data into plain text. It is often used to embed files in text, attach files to emails, or show data such as checksums.

Tom's Hardware says the problem is in a hand-written assembly routine. The routine fails a simple bounds check. If an attacker sends 64 As followed by an equals sign as padding, the input can overwrite nearby memory. The attacker can then use that corruption to run code. The report compares the memory corruption risk to Heartbleed, a well-known security flaw.

The report says the bug needs a specific hardware condition. The affected Java software must run on an x86-64 processor. That processor must support AVX-512 and the VBMI extension. x86-64 is a common processor type used in PCs and servers. AVX-512 and VBMI are processor features. In practice, that points to certain server chips. These include Intel's Ice Lake family and AMD's Zen 4 family, released in 2021 and 2022. Older CPUs are not affected because the faulty optimisation is specific to VBMI.

Which systems are affected

The report says many common products were vulnerable when it was published. Calif listed Keycloak, Jira, Confluence, Jenkins and PingFederate as having full unauthenticated remote code execution. That means an attacker could run code without first logging in.

The lab also listed Apache Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker as vulnerable after authentication. In those cases, an attacker would need some level of access before exploiting the flaw.

Java is also common in containers. Tom's Hardware says many container images that use Java-based applications are likely vulnerable. The exact number of affected images across registries is not given, but the report suggests it is high.

Because Java is so widespread, many vendors have had to respond. The report names IBM, Red Hat, Siemens and Broadcom among companies issuing advisories and updates. It also says the bug is unlikely to disappear quickly.

What to do next

Oracle has already released fixes and updated versions of its software. However, many programs bundle a separate Java executable. That means an Oracle fix alone may not protect every application.

Tom's Hardware says organisations should check vendor advisories and apply supplied updates. The report points to guidance from Oracle and other affected software makers. It also notes that companies such as IBM, Red Hat, Siemens and Broadcom have issued security notices.

The report says Calif found the flaw with the help of an AI bot, using $200 worth of tokens. It adds that this was not a simple case of poor code hygiene. The bug was in a deep optimisation path, which made it harder to spot.

For readers, the main risk is that Java-based services may be exposed across websites, business tools and devices. The safest step is to follow official vendor guidance and patch affected systems where updates are available.

Sources

  1. Critical Java vulnerability puts millions of sites, services, and devices at risk of remote code executionTom's Hardware

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.