// troubleshooting guide · jenkins

Jenkins Java4Shell (CVE-2026-114938) Vulnerability: How to Check and Fix Your Jenkins Controller

Status
Workaround available
platforms:
Jenkins controller and agents, Linux packages, Docker, Kubernetes, Windows
updated:
November 22, 2026
reports:
4
Method
how we research
Share

RUNBOOK · jenkins/java4shell-cve-2026-1149384 FIXES

// quick answer

Java4Shell (CVE-2026-114938, disclosed 17 Nov 2026) is a critical OpenJDK Base64 bug; its finder reports unauthenticated RCE against Jenkins in default configuration. The Jenkins project's fix: upgrade Java to a fixed build and restart, or add -XX:-UseBASE64Intrinsics to JAVA_OPTS.

Most likely fix: Check whether your controller is exposed

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Check whether your controller is exposed

    1. 01Open Manage Jenkins > System Information and read java.version and java.home
    2. 02Fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 or later; the build number must include the trailing .1
    3. 03On the controller host: grep -o -w -m1 'avx512vbmi' /proc/cpuinfo. No output means the vulnerable path cannot run on that CPU, but patch anyway
    4. 04Agents: the Jenkins post covers controllers only. Agents run their own Java; patch them too, since builds can decode untrusted Base64 (for example from pulled artifacts or webhooks)
    Did this fix it?
  2. FIX 2Apply the temporary JVM flag now

    1. 01Add -XX:-UseBASE64Intrinsics to JAVA_OPTS and restart Jenkins
    2. 02Linux packages: systemctl edit jenkins, set Environment="JAVA_OPTS=-XX:-UseBASE64Intrinsics ..." (keep your existing options), then systemctl daemon-reload and restart
    3. 03Docker: docker run --env JAVA_OPTS="-XX:-UseBASE64Intrinsics" jenkins/jenkins:lts-jdk21 (or your tag)
    4. 04Kubernetes/Helm: set controller.javaOpts and roll out the update
    5. 05Windows: add the flag to the <arguments> tag in jenkins.xml and restart the Jenkins service
    6. 06Confirm the flag appears in the JAVA_OPTS value under System Information > Environment Variables
    Did this fix it?
  3. FIX 3Upgrade Java

    1. 01Install a fixed Temurin or other vendor build (17.0.21.1, 21.0.13.1 or 25.0.5.1 or later) and restart Jenkins
    2. 02Docker: pull the current jenkins/jenkins LTS tag and check the bundled Java version in System Information. The Jenkins post showed lts-jdk25 on Java 25.0.5, but it did not list which tags are fixed, so verify your tag shows a .1 build before dropping the flag
    3. 03Rebuild custom agent images on a fixed base image
    Did this fix it?
  4. FIX 4Reduce exposure while you patch

    1. 01Put Jenkins behind VPN or SSO and disable anonymous read access
    2. 02Jenkins published guidance as a blog post (18 Nov 2026), not a formal security advisory, as far as we found; check jenkins.io/security/advisory for updates
    3. 03Review recent build and access logs if the controller was internet-facing
    Did this fix it?

SANDBOX · jenkins RUNS IN YOUR BROWSER

Try it: push, review, run CI and merge in a code host and cloud workspace

A hands-on Jenkins-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.

Symptoms

No visible symptom: this is a security exposure, not an outage. Scanners flag CVE-2026-114938 on your Jenkins controller, or Manage Jenkins > System Information shows Java 17, 21 or 25. Only controllers on a CPU with AVX-512 VBMI are exposed. Only hosts running Java 17, 21 or 25 on x86-64 CPUs with AVX-512 VBMI are exposed. As of 21 Nov 2026 the reports we checked described attack probes but no confirmed in-the-wild compromise, and the finder says there is no universal exploit: an attacker needs an application-specific way to deliver malicious Base64 data. Update 22 Nov 2026: the Jenkins post (18 Nov) still lists no fixed Docker image tags and we found no separate Jenkins security advisory for this CVE, so verify the Java version inside your image.

Why it happens

  • C-01Heap out-of-bounds write in the HotSpot AVX-512 VBMI Base64 decoding intrinsic in OpenJDK (CVE-2026-114938, found by Calif)
  • C-02Controller runs Java 17, 21 or 25 older than 17.0.21.1, 21.0.13.1 or 25.0.5.1
  • C-03Server CPU reports avx512vbmi, so the vulnerable path is used
  • C-04Jenkins reachable from the internet or a wide network without VPN/SSO in front. This is a Java runtime bug, not a Jenkins core or plugin bug, so updating Jenkins itself does not fix it

// this guide also covers

  • jenkins java4shell
  • CVE-2026-114938 jenkins
  • jenkins vulnerability november 2026
  • jenkins remote code execution fix

Still not working?

If Jenkins keeps failing, you're not alone. See every Jenkins problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Jenkins Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other Jenkins errors

All 15 Jenkins errors and fixes →