// troubleshooting guide · jira
Jira Java4Shell (CVE-2026-114938) Vulnerability: How to Check and Fix Jira Data Center
- Status
- Workaround available
- platforms:
- Jira Data Center, Jira Service Management Data Center, self-managed Linux/Docker
- updated:
- November 22, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · jira/java4shell-cve-2026-1149384 FIXES
// quick answer
Java4Shell (CVE-2026-114938, disclosed 17 Nov 2026) is a critical OpenJDK Base64 bug that researchers say allows unauthenticated remote code execution on self-hosted Jira. Fix by updating the Java runtime bundled with Jira, and until then add the JVM flag -XX:-UseBASE64Intrinsics.
Most likely fix: Check whether your Jira is exposed
How to fix it
// try these in order, the most common fix is first
FIX 1Check whether your Jira is exposed
- 01On the Jira host run java -version using the JRE Jira actually uses (the jre/ folder of the installer or the container image), not the system Java
- 02Fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 or later; anything older than that on a supported line is vulnerable
- 03Check the CPU: grep -oE '(avx512f|avx512bw|avx512vbmi|bmi2)' /proc/cpuinfo | sort -u. Fewer than four lines means the vulnerable code path cannot run on that host, but patch anyway in case you migrate to newer hardware
Did this fix it?FIX 2Apply the temporary JVM flag now
- 01Add -XX:-UseBASE64Intrinsics (or -XX:UseAVX=2) to JVM_SUPPORT_RECOMMENDED_ARGS
- 02Installer: edit bin/setenv.sh in your Jira install directory, put the flag inside the quotes of JVM_SUPPORT_RECOMMENDED_ARGS="", then restart Jira
- 03Docker: pass the flag through the JVM_SUPPORT_RECOMMENDED_ARGS environment variable and recreate the container
- 04Atlassian posted Data Center mitigation guidance on Atlassian Community; follow it for your exact product and version
Did this fix it?FIX 3Replace the bundled Java runtime
- 01Download a fixed Temurin (or other vendor) build and verify its checksum
- 02Back up and replace Jira's jre/ directory, keeping the old one for rollback
- 03For Docker, rebuild your image on top of the official Jira tag with the fixed JDK, and pin the tag
- 04Restart every Jira node so the new runtime is actually loaded, then keep the flag until all nodes are confirmed patched
Did this fix it?FIX 4Reduce exposure while you patch
- 01Atlassian's own interim advice (Data Center mitigation post) is the JVM flag in JVM_SUPPORT_RECOMMENDED_ARGS; it says patched releases will follow the fixed Temurin builds. As of 21 Nov 2026 no fixed version is published, so keep the flag and re-check the security bulletins page
- 02Put Jira behind VPN or SSO so unauthenticated requests cannot reach it
- 03Watch Atlassian's security bulletins page for an official advisory and a bundled-runtime update, and upgrade Jira when one ships
- 04Jira Cloud is run by Atlassian: no action is needed from you, and we found no report of Cloud customers being affected
Did this fix it?
SANDBOX · jira RUNS IN YOUR BROWSER
Try it: plan a sprint on a Jira-style board
A hands-on Jira-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. Security scanners flag CVE-2026-114938 on self-managed Jira Software or Jira Service Management (Data Center / Server) hosts, or your admin gets alerts about the OpenJDK Base64 flaw. Only hosts running Java 17.0.6 or later on x86-64 CPUs with AVX-512 VBMI are exposed. As of 19 Nov 2026 no in-the-wild exploitation was confirmed in the reports we checked. Atlassian's Data Center mitigation post covers Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management, rates the risk CVSS 9.2 and says out-of-cycle patches will follow once the fixed Temurin builds are bundled; as of 21 Nov 2026 we found no fixed Data Center version or patched 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-02Jira Data Center images and Linux installers bundle their own Temurin runtime, so OS package updates do not fix it
- C-03Server CPU supports avx512f, avx512bw, avx512vbmi and bmi2, so the vulnerable path is used
- C-04Jira reachable from the internet or a wide internal network without VPN/SSO in front
// this guide also covers
- jira java4shell
- CVE-2026-114938 jira
- jira data center vulnerability november 2026
- jira remote code execution fix
Still not working?
If Jira keeps failing, you're not alone. See every Jira problem users report or the alternatives people switch to.
Done fighting Jira? Our small team builds your own Jira alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usOther Jira errors
- Why Is Jira So Slow? Jira Running Slow Fixes
- Jira Not Loading: Blank Page or Spinning Board
- Jira Email Notifications Not Sending
- Jira Board Not Showing Issues
- Jira Automation Rule Not Triggering
- Jira Automation Limit Reached (Rules Throttled)
- Can't Log In to Jira (Login Page Keeps Refreshing)
- JQL Error: Field Does Not Exist or You Do Not Have Permission to View It