// troubleshooting guide · confluence
Confluence Java4Shell (CVE-2026-114938) Vulnerability: How to Check and Fix Confluence Data Center
- Status
- Workaround available
- platforms:
- Confluence Data Center, self-managed Linux/Windows/Docker
- updated:
- November 22, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · confluence/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 remote code execution against Confluence in default configuration. Atlassian posted a Data Center mitigation: add the JVM flag -XX:-UseBASE64Intrinsics, then move to a fixed Java runtime.
Most likely fix: Check whether your Confluence is exposed
How to fix it
// try these in order, the most common fix is first
FIX 1Check whether your Confluence is exposed
- 01Find the Java Confluence actually uses: the jre/ folder of the installer, or run java -version inside the container (docker exec -u confluence <container> java -version), not the system Java
- 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; anything older 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 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 the JVM arguments
- 02Installer: edit bin/setenv.sh in your Confluence install directory and add the flag to JVM_SUPPORT_RECOMMENDED_ARGS (keep any existing arguments), then restart Confluence. Check catalina.out after the restart to confirm the flag is in the java command line
- 03Windows service: run tomcat9w //ES//<SERVICENAME>, add the flag on its own line in the Java tab, restart the service
- 04Docker: pass the flag through the JVM_SUPPORT_RECOMMENDED_ARGS environment variable and recreate the container
- 05Atlassian posted 'Data Center mitigations for CVE-2026-114938' on Atlassian Community; follow it for your exact version
Did this fix it?FIX 3Replace the bundled Java runtime
- 01Download a fixed Temurin build (17.0.21.1, 21.0.13.1 or 25.0.5.1 matching your Confluence's Java line) and verify its checksum
- 02Back up and replace Confluence's jre/ directory, keeping the old one for rollback
- 03For Docker, rebuild your image on top of the official atlassian/confluence tag with the fixed JDK and pin the tag
- 04Restart every 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 Confluence behind VPN or SSO so unauthenticated requests cannot reach it
- 03Watch Atlassian's security bulletins for an official advisory and a bundled-runtime update; as of 19 Nov 2026 the Atlassian bulletin we checked did not list this CVE, so upgrade Confluence when a release with a fixed JRE ships
- 04Check any Confluence-adjacent Java apps (Jira, Bitbucket, Bamboo) the same way
Did this fix it?
SANDBOX · confluence RUNS IN YOUR BROWSER
Try it: write, sync and search notes on two devices
A hands-on Confluence-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 self-managed Confluence Data Center hosts, or your admin gets alerts about the OpenJDK Base64 flaw. 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. Atlassian Cloud is run by Atlassian and needs no action from you. 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-02Confluence installers and the atlassian/confluence Docker images bundle their own Temurin runtime, so OS Java updates do not fix it. Third-party testing reported the images we could see (Confluence 11.0.1 on Temurin 25.0.5+8, 10.2.20 and 9.x on Temurin 21.0.13+9) were still on vulnerable builds
- C-03Server CPU supports avx512f, avx512bw, avx512vbmi and bmi2, so the vulnerable path is used
- C-04Confluence reachable from the internet or a wide internal network without VPN/SSO in front
// this guide also covers
- confluence java4shell
- CVE-2026-114938 confluence
- confluence data center vulnerability november 2026
- confluence remote code execution fix
Still not working?
If Confluence keeps failing, you're not alone. See every Confluence problem users report or the alternatives people switch to.
Done fighting Confluence? Our small team builds your own Confluence alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usOther Confluence errors
- Why Is Confluence So Slow?
- Confluence Can't Save Changes Error
- Confluence Search Not Finding Pages
- Confluence You Cannot View This Page (Inherited Restrictions)
- How to Restore a Deleted Confluence Page
- Confluence PDF Export Not Working
- Confluence Cloud Migration Missing Attachments
- How to Cancel Confluence Subscription