Kivorent News

Wednesday, November 18, 2026

Tech and AINews

Oracle patches Java4Shell, an OpenJDK flaw researchers used to hijack Jira and Jenkins

Oracle patched CVE-2026-114938, a memory corruption flaw in Java's Base64 decoder that security firm Calif calls Java4Shell. Calif says it took over Jira, Confluence, Jenkins and Keycloak with it; no attacks have been reported yet.

Warden, covering security, outages and the rules for tech
, 3 min read

17.0.6First OpenJDK release Calif says is affected

What to know

  • CVE-2026-114938 is a memory corruption bug in OpenJDK's fast Base64 decoder on x86-64 processors with AVX-512 VBMI; ARM64 is not affected.
  • Oracle fixed it on November 17 in Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1; other Java distributions ship fixes on their own schedules.
  • Calif says it got remote code execution without logging in against default setups of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.

Oracle has patched CVE-2026-114938, a memory corruption flaw in the Java runtime that security firm Calif has named Java4Shell. Calif disclosed the bug on November 17, after Oracle shipped fixes that afternoon, and says it used the flaw to run its own code on default installs of Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate without logging in.

As of November 17, Tenable said it knew of no attacks using the flaw, and it was not in the Cybersecurity and Infrastructure Security Agency's (CISA) Known Exploited Vulnerabilities catalog. SecurityWeek reported that CISA issued an alert urging immediate patching, starting with systems exposed to the internet.

What the bug is

The flaw sits in a hardware-accelerated version of Java's Base64 decoder, a routine that turns encoded text back into bytes. Many servers decode Base64 from requests sent by strangers, in login tokens, headers and uploaded data.

According to Calif, the decoder's AVX-512 VBMI code path on x86-64 processors miscalculates how much to write when the input ends in a padding character. A fixed 64-byte write then runs past a 50-byte buffer. Calif says a string of 64 letter "A"s followed by "=" is enough to trigger it, or 128 on OpenJDK 17. ARM64 machines are not affected, and neither are x86-64 chips without that instruction set.

Calif says the bug affects OpenJDK 17.0.6 and newer and every distribution built from it, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, the Microsoft Build of OpenJDK, Azul Zulu, Red Hat's OpenJDK and SAP SapMachine. Tenable notes the OpenJDK advisory lists Java 17, 21, 25 and 27, not standard Java 8 or 11.

How bad it is

Calif scores the flaw 9.2 out of 10 under the CVSS 4.0 system. Oracle scores it 8.1 under CVSS 3.1, describing it as remotely exploitable without authentication but with high attack complexity. The two numbers use different scales; our CVSS explainer covers why they differ.

There is no one-size exploit. Each application needs its own path for getting attacker-controlled Base64 to the decoder. Calif says it found such paths that work before login in six products, and after login in Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It published a short trigger that shows the memory corruption but is holding back the application-specific exploits.

VulnCheck told SecurityWeek that crashing a vulnerable Java process is easy once an entry point is found, but that turning the bug into code execution is much harder. Cisco Talos said it had not seen exploitation, though "we anticipate probing attempts may pick up soon," per SecurityWeek.

BleepingComputer reported that researcher Quang Luong found the bug in about an hour while auditing OpenJDK with OpenAI's Codex coding assistant. Calif says the AI usage cost less than $200.

What to do

Oracle's fixed releases, per Tenable, are Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, plus 8u513-perf for the Java 8 Enterprise Performance Pack. They are part of Oracle's November Critical Security Patch Update. Users of Corretto, Temurin, Zulu and other builds need their vendor's own fixed release; SecurityWeek reported that as of November 17 the fix was not yet in the public OpenJDK 17, 21 and 25 update repositories.

Until then, Calif suggests starting Java with -XX:-UseBASE64Intrinsics, which turns off the fast decoder, or -XX:UseAVX=2 on x86-64 only. Both are stopgaps. Applications such as Jira and Jenkins that bundle their own Java runtime will need updates from those vendors too. Our guide on how to read a security advisory explains how to check which version you run.

Why it matters

Java runs a large share of the self-hosted business software that companies expose to the internet, and this bug sits below all of it, in the runtime itself. The same products hit by Java4Shell were already under pressure this week: attackers exploited an Apache Axis flaw in Confluence Data Center, and the window between disclosure and attack keeps shrinking, as with recent zero-days. Teams that patch Java now, before working exploits spread, avoid the scramble that followed Log4Shell.

Sources

Internet, outages and security

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.