# Mitigating Java4Shell in Jenkins

**URL:** <https://community.jenkins.io/t/mitigating-java4shell-in-jenkins/37694>\
**Category:** Community\
**Tags:** docker, sig-security\
**Created:** [November 18, 2026, 10:29pm UTC](https://community.jenkins.io/t/mitigating-java4shell-in-jenkins/37694 "2026-11-18T22:29:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [November 18, 2026, 10:29pm UTC](https://community.jenkins.io/t/mitigating-java4shell-in-jenkins/37694/1 "2026-11-18T22:29:02Z")

</div>

[CVE-2026-114938](https://nvd.nist.gov/vuln/detail/cve-2026-114938) (“Java4Shell”) is a heap overflow vulnerability in OpenJDK’s hardware-accelerated Base64 decoder affecting Java 17, 21, and 25 running on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake or newer; AMD Zen 4 or newer).

The issue is fixed in the November 2026 Java releases 17.0.21.1, 21.0.13.1, and 25.0.5.1. Upgrade Java and restart Jenkins to fix the issue.

If you cannot immediately upgrade Java, add the JVM startup flag -XX:-UseBASE64Intrinsics to your Jenkins controllers and restart Jenkins.

The [Eclipse Temurin blog post](https://adoptium.net/news/2026/11/temurin-november-2026-cspu-java4shell) describes their plans to deliver 17.0.21.1, 21.0.13.1, and 25.0.5.1

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [November 19, 2026, 4:32am UTC](https://community.jenkins.io/t/mitigating-java4shell-in-jenkins/37694/2 "2026-11-19T04:32:04Z")

</div>

An interesting assessment of the likelihood of a remote code execution is discussed in a blog post at:

> **[Java4Shell (CVE-2026-114938): Easy to Crash, Hard to Exploit — Less Than...](https://www.ox.security/blog/java4shell-cve-2026-114938-rce-risk/)**
>
> Java4Shell can crash vulnerable JVMs, but how widespread is the RCE risk? OX Research estimates just 0.12% of Java instances are exposed.

---

<div class="post-metadata">

**Author:** ![dduportal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/dduportal/32/18_2.png) [@dduportal](https://community.jenkins.io/u/dduportal)\
**Post date:** [November 19, 2026, 9:28am UTC](https://community.jenkins.io/t/mitigating-java4shell-in-jenkins/37694/3 "2026-11-19T09:28:14Z")

</div>

Regarding the Jenkins project Docker images, we are tracking fixed images in [Tracking container image fixes for CVE-2026-114938 (“Java4Shell”) i · Issue #2537 · jenkinsci/docker · GitHub](https://github.com/jenkinsci/docker/issues/2537)
