Our security team is investigating impact to Atlassian Cloud. Protecting our customers' data is our top priority, and we will communicate with customers directly if we determine there is any impact to their data. No Cloud customer action is required.
Hello,
Atlassian is aware of CVE-2026-114938, a vulnerability in a third-party library, OpenJDK. OpenJDK have classified this vulnerability as CVSS 8.1, which is high severity.
Atlassian has investigated our use of this platform in our Data Center products, and classified this as CVSS 9.2, which reflects the critical risk that this vulnerability represents to customer data. Out-of-cycle patches to fix this vulnerability will be released once third-party Temurin releases are made available.
In the interim, we’ve provided a mitigation at the conclusion of this post that is applicable to the latest versions of the following affected Data Center products in standard installation environments:
- Bamboo Data Center
- Bitbucket Data Center
- Confluence Data Center
- Crowd Data Center
- Jira Data Center
- Jira Service Management Data Center
If you have a non-standard installation, we recommend consulting your security team to determine whether these mitigations are appropriate for your installation.
Thank you,
Atlassian Support
Bamboo Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
Docker and Kubernetes based deployments:
Bamboo Agents
Remote agents
- Edit
<bamboo-agent-home>/conf/wrapper.conf wrapper.java.additional.x=-XX:+IgnoreUnrecognizedVMOptionswrapper.java.additional.x+1=-XX:UseAVX=2- Restart the remote agent
Remote Agent (Docker based)
Add this before the image name in your existing docker run command:
docker run -e JAVA_TOOL_OPTIONS='-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2' <rest of command>
Remote Agent (Kubernetes using the Atlassian Helm chart)
In your existing values.yaml, add:
agent: additionalEnvironmentVariables: - name: JAVA_TOOL_OPTIONS value: "-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"
Elastic agents
Linux
- Open Bamboo administration → Elastic Bamboo → Image configurations.
- Edit each applicable image configuration.
cat > /etc/profile.d/bamboo-agent-jvm-workaround.sh <<'EOF'export JAVA_TOOL_OPTIONS="${JAVA_TOOL_OPTIONS:+${JAVA_TOOL_OPTIONS} }-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"EOFchmod 0644 /etc/profile.d/bamboo-agent-jvm-workaround.sh- Save the configuration.
Windows
- Open Bamboo administration → Elastic Bamboo → Image configurations and edit each applicable Windows image configuration.
- @echo off
setlocal DisableDelayedExpansionset "LAUNCHER=C:\opt\bamboo-elastic-agent\bin\bamboo-elastic-agent.bat"if not exist "%LAUNCHER%" ( echo ERROR: Elastic agent launcher not found: %LAUNCHER% >&2 exit /b 1)findstr /L /C:"BAMBOO_JVM_WORKAROUND_JAVA_TOOL_OPTIONS" "%LAUNCHER%" >nulif errorlevel 2 exit /b 1if not errorlevel 1 exit /b 0if not exist "%LAUNCHER%.pre-jvm-workaround" ( copy /y "%LAUNCHER%" "%LAUNCHER%.pre-jvm-workaround" >nul if errorlevel 1 exit /b 1)( echo @rem BAMBOO_JVM_WORKAROUND_JAVA_TOOL_OPTIONS echo @set "JAVA_TOOL_OPTIONS=%%JAVA_TOOL_OPTIONS%% -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2" type "%LAUNCHER%") > "%LAUNCHER%.jvm-workaround.tmp"if errorlevel 1 exit /b 1move /y "%LAUNCHER%.jvm-workaround.tmp" "%LAUNCHER%" >nulif errorlevel 1 exit /b 1 - Save the configuration.
Ephemeral agents
- Open Bamboo administration → Ephemeral agents → Templates.
- Edit each applicable pod template.
- name: JAVA_TOOL_OPTIONS value: "-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"- Save and validate the template.
Bitbucket Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
The following sections detail how to do this for each part of a Bitbucket DC system.
Bitbucket DC webapp
All Bitbucket DC customers should apply the following fixes to the main Bitbucket DC webapp. If you have a multi-node cluster, apply these fixes to each node in the cluster. After applying the fixes, each node must be restarted.
First, patch the main Java VM using one of the two following options:
Option 1: Set the JVM_SUPPORT_RECOMMENDED_ARGS environment variable on your system
JVM_SUPPORT_RECOMMENDED_ARGS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"- If you already have this environment variable defined, you may append the two options above, ensuring there is a space between the new options and any existing options.
Option 2: Edit the bin/_start-webapp.sh file in the Bitbucket install directory
- Find the line
#JVM_SUPPORT_RECOMMENDED_ARGS= and change it to:
JVM_SUPPORT_RECOMMENDED_ARGS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2" - If this variable already has other options defined, you may append the two options above, ensuring there is a space between the new options and any existing options.
- If you upgrade Bitbucket, remember to re-apply the patch to the new installation.
Then, patch the Java VM used by the Mesh sidecar. Edit the file <BITBUCKET_HOME>/shared/bitbucket.properties. If this file doesn’t exist, create it.
Add the following lines to the end of the file:
plugin.bitbucket-git.mesh.sidecar.jvm-args[0]=-XX:+IgnoreUnrecognizedVMOptionsplugin.bitbucket-git.mesh.sidecar.jvm-args[1]=-XX:UseAVX=2
After applying the above fixes to a node, restart the node.
Mirrors
Each Bitbucket mirror and each node in a Bitbucket mirror farm should be patched as per the instructions in “Bitbucket DC webapp”.
Mesh nodes
If your Bitbucket DC system uses seperate, remote Mesh nodes, apply the following fixes to each Mesh node. After applying the fixes, each node must be restarted.
Patch Mesh’s Java VM using one of the two following options:
Option 1: Set the JVM_SUPPORT_RECOMMENDED_ARGS environment variable on your system
JVM_SUPPORT_RECOMMENDED_ARGS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"- If you already have this environment variable defined, you may append the two options above, ensuring there is a space between the new options and any existing options.
Option 2: Edit the bin/_start-mesh.sh file in the Bitbucket install directory
- Find the line
JVM_REQUIRED_ARGS="$JVM_MEMORY_ARGS $JVM_FILE_ENCODING_ARGS $JVM_JAVA_ARGS" and change it to JVM_REQUIRED_ARGS="$JVM_MEMORY_ARGS $JVM_FILE_ENCODING_ARGS $JVM_JAVA_ARGS -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2" - If you upgrade Bitbucket Mesh, remember to re-apply the patch to the new installation.
After applying one of the above fixes to a node, restart the node.
Open Search
The following steps will fix the Java VM used when running Bitbucket’s bundled Open Search server. If you run an external Open Search server, contact your vendor for patch instructions.
These steps only apply if:
- You are running Bitbucket 9.x or before (Open Search is not bundled with Bitbucket 10 and above)
- You are running a single-node Bitbucket system (the bundled Open Search server cannot be used with clustered systems)
- You are using the Open Search server bundled with Bitbucket (not an external Open Search instance)
Edit the bin/_start-search.sh file in the Bitbucket install directory.
Near the bottom of the file is the block of code that starts Open Search:
# Start OpenSearch (which requires passing the config path and tmp directory path). Note that OpenSearch is always# started in the background, even in "run" mode.# Filter stderr via the filter_warn function, take stdout from the function and print that to stderrOPENSEARCH_PATH_CONF="$OPENSEARCH_CONFIG_PATH" OPENSEARCH_TMPDIR="$OPENSEARCH_TMPDIR" "$OPENSEARCH_DIR/bin/opensearch" -d -p "$OPENSEARCH_PID" 2> >(filter_warn >&2)
Edit the line starting with OPENSEARCH_PATH_CONF as below (prepending the OPENSEARCH_JAVA_OPTS value):
OPENSEARCH_JAVA_OPTS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2 $OPENSEARCH_JAVA_OPTS" OPENSEARCH_PATH_CONF="$OPENSEARCH_CONFIG_PATH" OPENSEARCH_TMPDIR="$OPENSEARCH_TMPDIR" "$OPENSEARCH_DIR/bin/opensearch" -d -p "$OPENSEARCH_PID" 2> >(filter_warn >&2)
After applying the above, restart the Open Search server.
Docker
If you use the official Bitbucket DC Docker image, can set the JVM_SUPPORT_RECOMMENDED_ARGS environment variable with the -e option:
docker run -e 'JVM_SUPPORT_RECOMMENDED_ARGS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"' <rest of command>
Fix the container’s Mesh sidecar by editing the container’s /var/atlassian/application-data/bitbucket/shared/bitbucket.properties file. If this file doesn’t exist, create it.
Add the following lines to the end of the file:
plugin.bitbucket-git.mesh.sidecar.jvm-args[0]=-XX:+IgnoreUnrecognizedVMOptionsplugin.bitbucket-git.mesh.sidecar.jvm-args[1]=-XX:UseAVX=2
Restart the container.
Confluence Data Center
For standard deployments:
- Pass the following JVM flags to the application at startup:
For Linux <confluence-install>/bin/setenv.sh:
CATALINA_OPTS="-XX:UseAVX=2 -Dconversion.sandbox.java.options=\"-XX:+IgnoreUnrecognizedVMOptions,-XX:UseAVX=2\" ${CATALINA_OPTS}"
For Windows Service (add as a new line) in the Java Options box:
-XX:UseAVX=2-Dconversion.sandbox.java.options=-XX:UseAVX=2,-XX:+IgnoreUnrecognizedVMOptions
See Configuring System Properties | Confluence Data Center 11.0 | Atlassian Documentation
- Update
<confluence-home>/synchrony-args.properties and/or <confluence-shared-home>/synchrony-args.properties (if the file is present) with these two new lines:
synchrony.jvm.arg.jdk1=-XX:+IgnoreUnrecognizedVMOptionssynchrony.jvm.arg.jdk2=-XX:UseAVX=2
- Restart Confluence
For Kubernetes:
Redeploy Confluence with these Helm Chart values:
confluence: additionalJvmArgs: - -XX:UseAVX=2 - -Dconversion.sandbox.java.options=-XX:+IgnoreUnrecognizedVMOptions,-XX:UseAVX=2synchrony: additionalJvmArgs: - -XX:+IgnoreUnrecognizedVMOptions - -XX:UseAVX=2
For Docker:
Redeploy the Confluence Docker container with the -XX:UseAVX=2 appended into JVM_SUPPORT_RECOMMENDED_ARGS.
docker run -e JVM_SUPPORT_RECOMMENDED_ARGS="-XX:UseAVX=2 -Dconversion.sandbox.java.options=-XX:+IgnoreUnrecognizedVMOptions,-XX:UseAVX=2" <rest of command>
Crowd Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
Further details can be found here:
Jira Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
Further details can be found here: Setting properties and options on startup | Administering Jira applications Data Center 11.3 | Atlassian Documentation
Jira Service Management Data Center
To mitigate this issue, please add the following JVM arguments to your environment and restart services.
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions
Further details can be found here: Setting properties and options on startup | Administering Jira applications Data Center 11.3 | Atlassian Documentation