Security News

Java4Shell: Critical Java Flaw Puts Popular Business Apps at Risk of Remote Takeover

The Register · 18 Nov 2026
Key Takeaway Work out which of your business applications run on Java, then apply Oracle's fixed Java versions to internet-facing systems first.

The US Cybersecurity and Infrastructure Security Agency (CISA) has urged Java users to patch a high-severity flaw straight away. Attackers can use it to crash the Java virtual machine (JVM) or, in some cases, run their own code remotely without logging in. Oracle disclosed the issue (CVE-2026-114938) in its November patch release, which contained 655 fixes across 62 products.

The flaw was found by security research firm Calif.io, which named it Java4Shell. It is a memory-corruption bug in the Base64 decoder in OpenJDK. Base64 is a common way of representing binary data as text, used in authentication, file uploads and network messages. Calif says malformed input can overwrite neighbouring memory, which could expose sensitive data or lead to code execution. It scored the flaw 9.2 out of 10 (critical) under CVSS 4.0, and claims news of the bug leaked before Oracle's fixes were public.

Calif tested the flaw and found that Keycloak, Jira, Confluence, Jenkins, Apache Kafka Broker and Elasticsearch are susceptible to remote code execution. SentinelOne notes that any Base64 value passed to Java's decoder could carry an attack, including HTTP Basic credentials, SAML artifacts and CSRF tokens, and that in default configurations attackers can reach this code before authentication. Cisco Talos says affected systems run OpenJDK Java 17.0.6 and later on x86-64 CPUs with AVX-512 VBMI support enabled. Talos has not seen attacks in the wild yet but expects probing soon after disclosure, and believes the attack surface is likely larger than the apps tested so far.

Oracle's November update also fixed six flaws rated 10.0, in Access Manager, Oracle Platform Security for Java, WebLogic Server and Business Intelligence Enterprise Edition, plus five rated 9.9. Not everyone praised Calif's approach: an Akamai security architect criticised the firm's publicity focus.

Why it matters

Because the bug sits in Java's standard library rather than in one product, any application using the Base64 decoder may be exposed, so patching only the named apps is not enough. Attackers can reach the vulnerable code before authentication in default setups, which means login protection does not defend these systems. With Talos expecting probing soon and a leak claimed before disclosure, the window between patch release and attack may be short.

What to do

  • Install the fixed Java versions Oracle released in its November update.
  • Check whether your servers run OpenJDK 17.0.6 or later on x86-64 CPUs with AVX-512 VBMI enabled.
  • Start the JVM with AVX-512 support disabled as a temporary mitigation where patching is not yet possible.
  • Prioritise Keycloak, Jira, Confluence, Jenkins, Kafka and Elasticsearch deployments, and watch for probing attempts.
Java OpenJDK Java4Shell RCE Oracle patches CISA

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