// troubleshooting guide · bitbucket

Bitbucket Java4Shell (CVE-2026-114938) Vulnerability: How to Check and Fix Bitbucket Data Center

Status
Workaround available
platforms:
Bitbucket Data Center, self-managed Linux/Docker
updated:
November 22, 2026
reports:
4
Method
how we research
Share

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

// quick answer

Java4Shell (CVE-2026-114938, disclosed 17 Nov 2026) is a critical OpenJDK Base64 bug. Self-managed Bitbucket Data Center runs on Java (the official image used Temurin 21.0.13+9, a vulnerable build). Atlassian lists Bitbucket in its interim mitigation: add -XX:-UseBASE64Intrinsics, then update the runtime.

Most likely fix: Check whether your Bitbucket is exposed

How to fix it

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

  1. FIX 1Check whether your Bitbucket is exposed

    1. 01Find the Java Bitbucket actually uses: the JRE bundled in the installer directory, or JRE_HOME / BITBUCKET_JAVA_HOME if you set one, or java -version inside the container
    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; anything older on a supported line is vulnerable
    3. 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?
  2. FIX 2Apply the temporary JVM flag now

    1. 01Add -XX:-UseBASE64Intrinsics (or -XX:UseAVX=2) to JVM_SUPPORT_RECOMMENDED_ARGS
    2. 02Installer: add it to JVM_SUPPORT_RECOMMENDED_ARGS in bin/set-jre-home.sh / the Bitbucket environment settings (or as the JVM_SUPPORT_RECOMMENDED_ARGS environment variable), then restart Bitbucket. We could not verify the exact file for every version, so use the one from Atlassian's post
    3. 03Docker: pass the flag through the JVM_SUPPORT_RECOMMENDED_ARGS environment variable and recreate the container
    4. 04Atlassian posted 'Data Center mitigations for CVE-2026-114938' on Atlassian Community and names Bitbucket; follow it for your exact version
    5. 05Restart every node of a clustered setup
    Did this fix it?
  3. FIX 3Replace the bundled Java runtime

    1. 01Download a fixed Temurin 21.0.13.1 (or the build for your Java line) and verify its checksum
    2. 02Point Bitbucket at it (replace the bundled JRE or set the supported JRE home), keeping the old one for rollback
    3. 03For Docker, rebuild your image on top of the official atlassian/bitbucket tag with the fixed JDK and pin the tag
    4. 04Verify the running JVM version after restart and keep the flag until all nodes are patched
    Did this fix it?
  4. FIX 4Reduce exposure while you patch

    1. 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
    2. 02Put Bitbucket behind VPN or SSO and restrict who can reach the web and SSH endpoints
    3. 03Watch Atlassian's security bulletins for an official advisory and a bundled-runtime update; as of 19 Nov 2026 no Bitbucket-specific fixed release was named in what we checked
    4. 04Review audit logs for unusual requests if the host was internet-facing
    Did this fix it?

SANDBOX · bitbucket RUNS IN YOUR BROWSER

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

A hands-on Bitbucket-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 Bitbucket Data Center hosts. 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. Reports name Jira, Confluence, Jenkins and Keycloak as demonstrated targets; we found no report of a working Bitbucket exploit, but the Java runtime is the same. Bitbucket 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-02Bitbucket Data Center installers and the atlassian/bitbucket Docker image bundle their own Temurin runtime, so OS Java updates do not fix it. The latest image was reported on Temurin 21.0.13+9, which is vulnerable
  • C-03Server CPU supports avx512f, avx512bw, avx512vbmi and bmi2, so the vulnerable path is used
  • C-04Bitbucket reachable from the internet or a wide network without VPN/SSO in front

// this guide also covers

  • bitbucket java4shell
  • CVE-2026-114938 bitbucket
  • bitbucket data center vulnerability november 2026
  • bitbucket remote code execution fix

Still not working?

If Bitbucket keeps failing, you're not alone. See every Bitbucket 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 Bitbucket 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 Bitbucket errors