VulnerabilitiesApplication Security

Java4Shell: The Base64 Decoder Is the New Front Door

November 18, 2026 · Brian Deitch

This is my security story of the day. CISA put out an alert yesterday telling everyone to patch Java. Not a Java app. Java.

The bug is called Java4Shell (CVE-2026-114938), and the reason it matters is boring in the best way: Base64 decoding happens everywhere. Auth headers, tokens, file uploads, API payloads. If your Java app takes Base64 from the internet, and almost all of them do, it's worth an hour of your day today.

What We Know

  • The bug: a memory corruption flaw in the Base64 decoder of the x86-64 HotSpot JVM. Tenable's plain-English version: "Java4Shell is a flaw in how Java decodes Base64 data." Specifically, a performance shortcut that decodes Base64 faster on certain Intel and AMD chips can be fed a crafted string that makes it write past its buffer.
  • What it can do: crash the JVM, leak application memory (keys, tokens), or, with an application-specific exploit, run code. CISA says crafted input "could crash the JVM and allow for unauthenticated remote code execution."
  • Severity: Oracle scores it 8.1 (CVSS 3.1) with high attack complexity. Calif, the firm that found it, scores it 9.2 under CVSS 4.0.
  • The hardware catch: only x86-64 CPUs with AVX-512 VBMI are affected. That's Intel Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids Xeons, and AMD Zen 4 or newer. In other words, a lot of current cloud and data center hardware. ARM64 isn't affected.
  • Affected Java: OpenJDK lists the 17, 21, 25 and 27 lines. Calif says OpenJDK 17.0.6 and later are affected, along with the usual distributions built on it (Corretto, Temurin, Microsoft's build, Zulu, Liberica, SapMachine, Red Hat's and Oracle's OpenJDK). Standard Java 8 and 11 aren't on the OpenJDK list.
  • Fixed: Oracle's November 17 update ships 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 and 8u513-perf. Other distributions are shipping on their own schedules.
  • Exploitation: as of yesterday, Tenable says it isn't aware of any, and The Hacker News reports no evidence of exploitation in the wild. It isn't on CISA's KEV list. CISA issuing a standalone alert anyway tells you how seriously it's taking the reach of this one.

Credit where it's due: Calif (Quang Luong and Albert Yang) reported it, and Calif is holding back product-specific exploit chains until people have had time to patch. Calif says it used AI tooling to find the bug quickly. The practical takeaway isn't scary, it's scheduling: the gap between "a fix ships" and "someone has a working exploit" keeps shrinking, so your patch cycle for internet-facing runtimes has to shrink with it.

Who's Exposed

Calif's testing (not exhaustive) found default configurations reachable before login in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and after login in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. It also ran code on sample Struts and Spring Boot apps. Others have pointed at Tomcat Basic auth and JWT libraries as pre-login paths.

Two less obvious angles:

  • Clients, not just servers. Per Tenable, citing Calif, a Java program can be hit just by connecting over TLS to an attacker-controlled server. Your outbound traffic is attack surface too.
  • Java you didn't install. CISA specifically calls out runtimes bundled in third-party apps, container images and appliances. That's the long tail, and it's where Log4Shell lived for years.

What To Do

  • Inventory first. Find every JDK and JRE, including the ones hiding in vendor appliances and container base images. If you have SBOMs, this is the day they pay rent.
  • Patch internet-facing Java first: identity providers (Keycloak, PingFederate), CI/CD (Jenkins, Artifactory), collaboration (Jira, Confluence), and anything that decodes Base64 from unauthenticated users.
  • Check the hardware. On Linux, /proc/cpuinfo showing avx512vbmi (with avx512f, avx512bw and bmi2) means the vulnerable path is live.
  • Can't patch yet? Calif's workaround is -XX:-UseBASE64Intrinsics, which turns off the fast path. -XX:UseAVX=2 also works on x86-64, but Java on ARM won't start with it, so don't push it fleet-wide blindly. Neither Oracle nor OpenJDK lists these, so test before you rely on them.
  • Compensating controls, per CISA: restrict and validate Base64 input at the edge, enforce input size limits, and cut unauthenticated access where you can.
  • Watch for crashes. A JVM that starts dying on malformed auth headers is a signal, not a nuisance. Blackpoint reproduced a crash on a Spring Boot app in about 20 seconds of malformed requests.
  • Ask your vendors. "Which Java do you ship, and when is the fix?" is a fair question for every appliance and SaaS connector you run on-prem.

I work at Zscaler, so my bias is that the less of this you publish directly to the internet, the less a bug like this can do to you. But that's a long-term fix. Today's fix is a patch.

Update, November 19: Exploitation attempts have started, but no successful compromise has been confirmed. Per SecurityWeek, GreyNoise saw over 150 Java4Shell-shaped requests from five IPs by early November 19 with no successful intrusions on its sensors, watchTowr saw "java4shell-recon" scanners and blind attempts it called not "particularly functional or scary yet," Cloudflare's Cloudforce One saw scanners disguising themselves, and Previdian logged nine attempts from six IPs. VulnCheck has a full RCE exploit for its customers, so expect public ones to follow. It still isn't on CISA's KEV list. Vendor advisories are landing: Red Hat rates it Critical across RHEL 8, 9 and 10; Elastic says Elasticsearch RCE needs read-or-higher credentials but a crash doesn't; Keycloak's 26.8.2-1 and -2 images shipped the vulnerable JDK and 26.8.2-3 fixes it; Jenkins says update Java and restart; Atlassian says cloud needs no action and Data Center admins can disable AVX-512 as a workaround; Siemens recommends taking three Industrial Edge Management products offline; and Cisco lists more than a dozen affected products with no fix yet. My employer's ThreatLabz team also published its own write-up, with behavioral hunting tips (JIT warm-up floods of valid Base64, malformed Base64 tails, hs_err_pid crash logs in base64_decodeBlock) and a note that reverse-proxy request buffering helps but isn't a full mitigation. Same advice as yesterday, with more urgency: patch the internet-facing Java first. Sources: SecurityWeek, GreyNoise, Zscaler ThreatLabz

Bottom Line

Java4Shell isn't Log4Shell. It needs specific CPUs, and real exploits are app-specific. But Java is everywhere, Base64 is everywhere, and the hardware it needs is what's in most new servers. Find your Java, patch the internet-facing stuff this week, and go ask your vendors what they're shipping.

Sources: The Hacker News, Tenable FAQ, The Record, CISA alert

java4shellcve-2026-114938openjdkjavahotspotbase64avx-512cisapatch-managementsbom
All postsDiscuss on LinkedIn