---
title: "Java4Shell: critical OpenJDK flaw reportedly exposes Jenkins and Jira"
description: "A critical flaw dubbed Java4Shell, disclosed on 17 November 2026, reportedly sits in OpenJDK's Base64 decoder and allows remote code execution. Jenkins, Jira, Confluence and Keycloak are said to be exposed without authentication, and patches are already out."
canonical: https://inyourgeek.com/en/articles/2026-11-18-java4shell-une-faille-critique-d-openjdk-exposerait-jenkins-et
type: article
author: "Sébastien Soulier"
publisher: "InYourGeek"
language: en
datePublished: 2026-11-18
dateModified: 2026-11-18
section: "Security"
tags: ["java", "openjdk", "faille", "rce"]
---
# Java4Shell: critical OpenJDK flaw reportedly exposes Jenkins and Jira
> A critical flaw dubbed Java4Shell, disclosed on 17 November 2026, reportedly sits in OpenJDK's Base64 decoder and allows remote code execution. Jenkins, Jira, Confluence and Keycloak are said to be exposed without authentication, and patches are already out.
November 18, 2026 · Security · 3 min
On Tuesday 17 November 2026, researchers at the security firm Calif disclosed a vulnerability in OpenJDK, the open source implementation of Java. It goes by CVE-2026-114938 and, because every Java bug now needs a stage name, Java4Shell. A note on method: as we write this, on Wednesday 18 November, we have exactly one source, [Bleeping Computer's article](https://www.bleepingcomputer.com/news/security/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications/). Read everything below with a "reportedly" attached.

## Memory corruption in the Base64 decoder

According to Bleeping Computer, the defect sits in the hardware-accelerated version of Java's Base64 decoder. That component handles encoded data found in authentication, file uploads and network communications, which is to say most places you would rather not have a bug. Specially crafted Base64 data would cause the decoder to overwrite portions of Java's memory, opening the door to the disclosure of sensitive information or to remote code execution.

The trigger described by the researchers is short: 64 "A" characters followed by an equals sign. Older versions of OpenJDK 17 would need 128. As payloads go, it looks less like an exploit and more like a cat asleep on a keyboard.

Severity comes with two opinions. Calif rates the flaw 9.2 under CVSS 4.0, which is critical. Oracle gives it 8.1 under CVSS 3.1, which is high.

## Who would be exposed

The flaw reportedly affects OpenJDK from version 17.0.6 onwards, along with the distributions built on the same code: Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.

One hardware condition narrows the field: only the accelerated decoding function is affected, and it is only used on x86-64 processors that support the AVX-512 VBMI instructions. For once, older hardware may be a security feature.

On the application side, the researchers say they achieved code execution in default configuration on two groups of software:

- **without authentication**: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate;
- **with authentication**: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.

Sample applications built on Apache Struts and Spring Boot were reportedly compromised as well.

## What limits exploitation

Still according to the source, there is no universal exploit. For each application, an attacker has to find the path that carries their Base64 data all the way to the vulnerable decoder. Calif has published a proof of concept that demonstrates the memory corruption, but not the full exploits used against the applications listed above. The article reports no exploitation observed in the wild.

## What to update

Oracle released the fixes on 17 November as part of its November Critical Patch Update, which addresses 655 vulnerabilities across its product range. The vendor recommends applying them as soon as possible. The source does not give the fixed version numbers: check your Java distribution's own advisory instead of trusting a number you read somewhere else.

If you cannot update right away, Calif suggests two stopgaps:

- start the JVM with `-XX:-UseBASE64Intrinsics`, which disables accelerated Base64 decoding;
- on x86-64, use `-XX:UseAVX=2`, which disables the AVX-512 instructions.

These are temporary workarounds. The real fix is updating the Java runtime, including the one quietly bundled inside your applications.

One last detail from the file: according to Calif, the flaw was found during an audit of OpenJDK's internals carried out with OpenAI's Codex assistant, in about an hour, followed by two more hours to reach a first working exploit, all for under 200 dollars of AI usage. So bug hunting now has a sticker price. Leaving your Java runtime unpatched is still billed separately, and the invoice has your name on it.
## Sources
- [Critical Java4Shell flaw allows RCE attacks on major Java applications](https://www.bleepingcomputer.com/news/security/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications/) — bleepingcomputer.com
_Article written with AI assistance from the cited sources, reviewed and approved by a human before publication._

---

Equivalent HTML page : https://inyourgeek.com/en/articles/2026-11-18-java4shell-une-faille-critique-d-openjdk-exposerait-jenkins-et
Published by InYourGeek — https://inyourgeek.com/en/a-propos
Method and safeguards : https://inyourgeek.com/en/methode
All articles : https://inyourgeek.com/en/archives
