Skip to main content

Java4Shell: What a Single Base64 String Teaches Us About Runtime Risk

Updated 2 min readMarkdown
Java4Shell: What a Single Base64 String Teaches Us About Runtime Risk

When a new vulnerability lands, most teams first ask: which product? With Java4Shell, the answer is any software that runs on Java and decodes user-supplied Base64.

On November 17, 2026, details of CVE-2026-114938 were published: an out-of-bounds write in the AVX-512 hardware path of OpenJDK's Base64 decoder. Calif, which found it, rates it 9.2 under CVSS 4.0; Oracle scores it 8.1 under CVSS 3.1. Versions 17.0.6 and later plus the 21, 25 and 27 lines are affected, but only on x86-64 CPUs with AVX-512 VBMI, meaning Intel Ice Lake and newer and AMD Zen 4 and newer. Oracle shipped a fix the same day.

Why this one is different

In Calif's tests with default configurations, Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate reached code execution without login, and Kafka, Solr, Elasticsearch, Gerrit and Spinnaker after login. Even a Java client connecting over TLS to an attacker's server is at risk. Discovery speed also stands out: the researcher found the bug with an AI coding assistant in about an hour, for under $200.

Threat status

As of disclosure, no exploitation in the wild has been reported and the flaw is not in CISA's KEV catalog. The public proof of concept only shows the memory corruption, but crashing a service is far easier than running code on it.

The bigger lesson for vulnerability management

Most asset inventories record the application name, not the runtime packaged inside it. Jira or Jenkins may ship with its own Java, and container images often carry a separate Java build of their own. If your scanner only sees the Java installed on the operating system, a large part of the attack surface stays hidden. Log4Shell taught this lesson, and Java4Shell repeats it: a complete inventory of runtimes matters as much as the patch itself.

Four things to do this week

  • Find every Java process, including runtimes bundled inside applications and container images.
  • Check the avx512vbmi flag in /proc/cpuinfo to see which servers are affected.
  • Move to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, or your distribution's fixed build, then restart the processes.
  • Until patched, enable -XX:-UseBASE64Intrinsics after a performance test, starting with internet-facing services.

Full details, fixed versions and workarounds: Java4Shell in OpenJDK

— Kazem Mortazavi, independent network-security consultant

About the author

  • Founder of Security Land and CEO of PRS, with 25+ years in ICT. I write practical, no-hype analysis of the latest vulnerabilities, zero-days and incidents — and what security and infrastructure teams should actually do next. Focus areas: network security, DLP, encryption/HSM, identity and threat intelligence. More at symantecland.com

No comments yet. Be the first to comment.

More from this blog