A flaw in Java itself reaches Jira, Jenkins and Keycloak on newer servers. Update Java and restart

By George Bailey   Published: 11/19/26   4 min read

Java4Shell is a memory bug in the code Java uses to decode Base64, the text encoding that carries login headers, tokens and file uploads. Calif, the firm that found it, ran code without a login on Keycloak, Jira, Confluence, Jenkins, Artifactory and PingFederate in their default setups.

Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.

There is a catch that shrinks the list. The broken code only runs on x86-64 processors with AVX-512 VBMI, which means recent Intel Xeon and AMD Zen 4 or newer chips. Oracle and OpenJDK shipped fixes on November 17, and CISA told organizations to patch right away.

The bug lives in Java itself, so the app on top of it can be fully patched and still exposed.

Oracle and OpenJDK fixed a Java4Shell flaw in the Base64 decoder

CVE-2026-114938 is an out-of-bounds write in the hardware-accelerated Base64 decoder of the HotSpot JVM. Oracle rates it 8.1 under CVSS 3.1 and marks attack complexity as high. Calif scores it 9.2 under CVSS 4.0.

OpenJDK lists Java 17, 21, 25 and 27 as affected, not Java 8 or 11. Calif says OpenJDK 17.0.6 and newer are affected, along with distributions built from it: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK and Oracle Java SE.

On exploitation: Tenable reports that GreyNoise has seen exploitation attempts but no confirmed successful compromise on its sensors as of November 18. VulnCheck and a researcher at Immersive say they have working exploits; neither has released one. The flaw is not in CISA’s Known Exploited Vulnerabilities catalog.

Which Java servers are exposed to Java4Shell

Most companies don’t track Java as a product. It ships inside identity servers, build servers, ticketing tools and vendor appliances, and CISA warns those copies may not show up in a software inventory. A team that patched Jira last week can still be running a vulnerable JDK underneath it.

The hardware rule is the fastest filter. Calif lists Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, plus AMD EPYC and Ryzen on Zen 4 or newer. ARM64 servers are not affected. Cloud instances on those Intel and AMD generations count, so check the instance type, not just the data center.

Update Java to 17.0.21.1, 21.0.13.1 or later and restart

Forward this

For whoever runs our servers and vendor appliances: a flaw in Java itself, called Java4Shell, lets attackers run code on apps such as Jira, Jenkins and Keycloak when the server has a recent Intel or AMD processor. Can someone list our Java-based systems, update Java on them to the November 17 builds and restart them? Vendor appliances may need the vendor’s own update.

Details

Hunt / verify

Source: CISA alert; Calif write-up

Sources

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].