Java4Shell reaches Jira, Confluence and Jenkins
Researchers ran code before login through a flaw in Java’s Base64 decoder. Which systems face CVE-2026-114938, and how can operators verify the fix?
Reviewed by Codex · 18 November 2026

Researchers at Calif ran code remotely on Jira, Confluence and Jenkins before signing in to any of them. The three applications relied on the same Java routine to turn Base64 text back into bytes. On certain processors, that routine could corrupt the application’s memory. Oracle released a fix for the flaw, known as Java4Shell (CVE-2026-114938), on 17 November 2026. Oracle security update · Swiss NCSC advisory
What Calif demonstrated
The Swiss NCSC lists six products in which Calif demonstrated code execution without an account. Alongside Jira, Confluence and Jenkins were Keycloak, PingFederate and JFrog Artifactory. Calif also demonstrated code execution with an authenticated account in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Those access requirements matter when deciding which services to patch first. NCSC findings
Code running inside the application inherits the service account’s access. For a build server, that can include the credentials it uses to deliver software. Memory corruption can also expose data held by the process or bring the service down. Canada’s Cyber Centre said in its 17 November alert that it knew of no active exploitation at the time. Cyber Centre alert
Why two servers running the same app can differ
The Java virtual machine (JVM) can use special processor instructions to decode Base64 faster. The flaw affects that accelerated decoder on certain x86-64 processors with AVX-512 VBMI support. Exposure requires a vulnerable Java build, the acceleration to be active and the application to pass untrusted data to that decoder. A service may decode credentials as part of checking a login, while the sender is still anonymous. ARM64 uses a different implementation. CERT-EU advisory · Red Hat bulletin
Oracle’s entry covers affected Java SE 17, 21, 25 and 27 builds, the specific Java 8 performance build 8u511b33-perf, and certain GraalVM releases. It gives the flaw 8.1 out of 10 under CVSS 3.1. Atlassian rates the risk to its Data Center products 9.2, or critical. For an individual installation, record the runtime supplier, full build number and processor features visible inside the virtual machine. Oracle risk matrix · Atlassian assessment
Who owns the update?
For self-managed Jira and Confluence Data Center, Atlassian published product-specific JVM settings to use while awaiting its patched releases. Follow the instructions for your installation and restart the affected services on each node. For Atlassian Cloud, the company said it was investigating the impact and required no action from customers. Atlassian Data Center and Cloud guidance
For Jenkins or an application you operate yourself, identify the Java executable that starts the service. A container image or product installer can carry a separate runtime even when the host operating system is up to date. For example, Oracle lists 17.0.21.1+4 as its 17 November JDK 17 build. Match other suppliers’ packages to their own advisory. Where a fix must wait, use the supplier’s temporary mitigation for the affected architecture and schedule the permanent update. Oracle release notes · Red Hat mitigation guidance
Verify the running service
Start with internet-facing services, identity providers and build infrastructure. After replacing a runtime or rolling out a rebuilt image, restart each affected JVM. Check the build actually running on every replica, then confirm that an ordinary login or build still works. Record the deployed build alongside the vendor advisory. An image sitting in the registry can be fully patched while yesterday’s container is still serving traffic. NCSC operator guidance