Incident sheet · /security

Filed
Read
4 min · 702 words
Severity
Routine

Java4Shell Flaw Exposes Jenkins, Jira and Keycloak to Remote Code Execution

Java4Shell, CVE-2026-114938, allows unauthenticated RCE on Jenkins, Jira, Confluence and Keycloak. Oracle patched it November 17 amid 655 CPU fixes.

Critical Java4Shell flaw allows RCE attacks on major Java applications
FeedCritical Java4Shell flaw allows RCE attacks on major Java applications — blickpixel / pixabay

Event log

  1. CVE-2026-114938, rated CVSS 9.2 by Calif and 8.1 by Oracle, enables unauthenticated RCE on six major Java applications including Jenkins and Keycloak.
  2. Oracle patched the flaw on November 17 within a Critical Patch Update covering 655 vulnerabilities.
  3. The bug affects OpenJDK 17.0.6 and later across Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.
  4. Researcher Quang Luong found the flaw in about one hour using OpenAI Codex, at an AI cost under $200.
  5. Temporary mitigation: -XX:-UseBASE64Intrinsics or -XX:UseAVX=2; full patching remains required.

A critical OpenJDK vulnerability rated 9.2 out of 10 enables unauthenticated remote code execution against Jenkins, Atlassian Jira, Confluence, Keycloak, JFrog Artifactory and PingFederate in their default configurations. Security firm Calif disclosed the flaw, tracked as CVE-2026-114938, on Tuesday. The nickname Java4Shell invites comparison to Log4Shell. The comparison only partly holds, and the differences matter for patch prioritization.

What exactly is the flaw?

Java4Shell is a memory-corruption bug in Java's hardware-accelerated Base64 decoding functionality. Crafted Base64 input can overwrite portions of Java's memory, allowing attackers to steal sensitive information or execute malicious code. Base64 processing runs through authentication flows, file uploads and network communications, so the attack surface is broad.

Calif rated the flaw critical at CVSS 4.0 9.2. Oracle scored it lower, at 8.1 High under CVSS 3.1. The one-point gap between vendor and researcher scoring is not explained in either disclosure. Treat both ratings as severe.

The affected range is wide: OpenJDK 17.0.6 and later, plus every distribution built from that code. The list includes Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. If your estate runs Java on any mainstream distribution, assume exposure until proven otherwise.

Which applications are actually exploitable?

Calif demonstrated exploitation against widely deployed enterprise software running default configurations. The company sorted its results into two tiers:

  • Unauthenticated RCE: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.
  • Authenticated RCE: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.

Researchers also exploited the bug in sample applications built on Apache Struts and Spring Boot. That extends the risk to in-house code, not just packaged products.

Two constraints temper the panic. Calif states plainly that Java4Shell has no universal exploit; attackers must find an application-dependent path to deliver malicious Base64 data to the decoder. The flaw also requires the hardware-accelerated decoding path, which activates only on x86-64 processors supporting AVX-512 instructions with VBMI capabilities. Older OpenJDK 17 versions require a longer trigger string — 128 "A" characters versus 64 — but the difference is trivial for an attacker.

How was it found, and at what cost?

Researcher Quang Luong discovered the flaw using OpenAI's Codex AI coding assistant during an audit of OpenJDK's internals. Calif says the discovery took roughly one hour, with an initial working exploit built in another two hours. Total AI usage cost came in under $200 — less than a single consultant-day in most markets. AI agents also helped develop additional application-specific exploitation chains.

That figure deserves scrutiny. Three hours and $200 covers one finding in one codebase by one researcher already skilled enough to validate it. It does not mean AI substitutes for a security team. Calif has published a proof-of-concept demonstrating memory corruption but withheld the weaponized exploits used against the enterprise applications. Expect that restraint to erode once researchers outside Calif begin reverse-engineering the patch.

What should CIOs do right now?

Oracle shipped fixes for CVE-2026-114938 on November 17 as part of its November Critical Security Update, which addressed 655 vulnerabilities across the product portfolio. Oracle recommends customers apply patches as soon as possible. Six hundred fifty-five fixes in one CPU means Java4Shell competes for attention with everything else in the queue.

For teams that cannot patch immediately, Calif offers two temporary mitigations:

  • Launch OpenJDK with -XX:-UseBASE64Intrinsics to disable the vulnerable hardware-accelerated Base64 path.
  • On x86-64 systems, use -XX:UseAVX=2 to disable AVX-512 instructions outright.

Both flags carry a performance cost on Base64-heavy workloads, and Calif itself calls them temporary. The end state is unchanged: update Java runtimes to the latest version. Inventory is the hard part, since Java ships embedded inside appliances, CI servers and vendor products that admins rarely audit directly.

The disclosure also lands a broader message in the boardroom. A one-hour, sub-$200 AI-assisted discovery against a platform running enterprise applications, web services and financial systems worldwide resets the economics of offensive research. Attackers read the same news. Patch cycles built on the assumption that exploitation takes weeks may no longer hold.

via bleepingcomputer.com (Source)

Filed under

  • java4shell
  • cve-114938
  • openjdk
  • remote-code-execution
  • ai-assisted-security-research
Share this article:

More from Daniel Okafor

Daniel Okafor

Show full bio

Staff writer covering technology and product news in enterprise information technology and the leaders who run at CIO Monitor.

203 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›