Skip to content
Rush Commerce
Software & Dev3 min read

Java4Shell CVE-2026-114938: patch Jira, Jenkins, Keycloak

Java4Shell is an OpenJDK Base64 bug Calif says gives pre-auth RCE on Jira, Confluence, Jenkins and Keycloak. Found with Codex in an hour. Patch or set the JVM flag.

Java4Shell (CVE-2026-114938) is a memory-corruption bug in OpenJDK's Base64 decoder, and it went public on Tuesday. The security firm Calif says it gives remote code execution, with no login, on Jira, Confluence, Jenkins and Keycloak in their default configs. Oracle shipped patched builds the same afternoon. The part that should change how you plan: Calif says one researcher found it with OpenAI's Codex in about an hour, for less than $200 in tokens.

What actually happened

Per Calif's write-up, CyberScoop and Endor Labs' analysis:

  • The bug: a heap overflow in HotSpot's hand-written AVX-512 Base64 decoder on x86-64. A crafted Base64 string with = padding writes past the end of its buffer.
  • Who's exposed: OpenJDK 17.0.6 and newer, plus 21, 25 and 27, on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake servers and later, AMD Zen 4 and later). ARM64 is not affected. That covers Corretto, Temurin, Zulu, Microsoft, Red Hat and Oracle builds too.
  • Pre-auth RCE, per Calif: Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. Post-auth: Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. CyberScoop reports Calif showed a working break-in against Keycloak.
  • Severity: Calif rates it 9.2 under CVSS 4.0. No independent score is out yet.
  • Exploits: Calif published only a safe trigger test and is holding back the product exploits until people patch.
  • In the wild: none reported as of Nov 17, and it is not on CISA's Known Exploited list. CyberScoop says CISA issued a notice to patch.

One open point: Endor says Java 8 and 11 are not affected, but Oracle's list to Calif names an 8u511 "perf" build. Check your vendor's advisory, not a blog, before you mark a box safe.

Why it matters for your business

Most small businesses don't write Java. They run it. The self-hosted Jira on a VM, the Jenkins box that builds your app, the Keycloak in front of your customer portal. That is where this bug lives.

Do this today:

  1. List every JVM you run. Include vendor appliances and containers. java -version on each.
  2. Upgrade the runtime to your vendor's November build. Endor lists OpenJDK 27.0.1.1 as fixed and Oracle 17.0.21.1 and 21.0.13.1 as reportedly fixed. Other vendors use their own version numbers.
  3. Can't patch tonight? Calif's workaround is to start the JVM with -XX:-UseBASE64Intrinsics. Endor's narrowest option is -XX:+UnlockDiagnosticVMOptions -XX:DisableIntrinsic=_base64_decodeBlock.
  4. Pull internet-facing tools behind a VPN until they're patched.

Then think about the hour. A bug in code that shipped in January 2023 took one person and one AI agent about 60 minutes to find. Attackers have the same tools. The gap between "bug exists" and "bug is used" is getting shorter, so your patch window has to get shorter too.

Key takeaways

  • Java4Shell is an OpenJDK Base64 heap overflow on AVX-512 x86-64 servers
  • Calif claims pre-auth RCE on Jira, Confluence, Jenkins, Keycloak, Artifactory and PingFederate
  • Patched builds shipped Nov 17; a JVM flag is a stopgap
  • No exploitation reported yet, and the product exploits are held back for now
  • A researcher found it with Codex in about an hour, so expect shorter patch windows

Do you know every server running Java in your business? We set up the inventory, the update path and the alerts so a Tuesday CVE is a 20-minute job, not a weekend. See what we build or send us your stack and we'll tell you what's exposed.

Sources: Calif, CyberScoop, Endor Labs.

  • #java4shell
  • #cve
  • #openjdk
  • #patching
  • #security
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.