CybersecurityIn the news

Java4Shell (CVE-2026-114938): Which Java Hosts Are Exposed and What to Patch First

Yahia Aboushadi
Director of Brand and Marketing, Pyramid Systems
Reading time:
6 min.

Whether Java4Shell can turn into a server takeover depends on three things: which Java build a host runs, which processor sits under it and whether outside data reaches a Base64 decode. The flaw, CVE-2026-114938, is the one the Cybersecurity and Infrastructure Security Agency (CISA) urged organizations to patch immediately on November 17, 2026, the day Oracle and the OpenJDK project released fixes. Every Java runtime should be updated; the three conditions decide the order.

What is Java4Shell?

It is a memory corruption bug in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine (JVM). CISA's alert says "specially crafted Base64 input could crash the JVM and allow for unauthenticated remote code execution." Oracle and OpenJDK credit Quang Luong of Calif and Albert Yang with the report.

The flaw lives in hand-written assembly that HotSpot uses to decode Base64 faster on newer processors. Calif says it reached unauthenticated remote code execution in the default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and that the same bug can leak heap memory holding keys, tokens and personal data. Oracle scores it 8.1 under CVSS 3.1 with high attack complexity; Calif scores it 9.2 under CVSS 4.0. Record which scale your tickets use.

Which Java versions are affected?

The answer depends on whose build you run. The OpenJDK advisory marks the 17, 21, 25 and 27 release lines for this CVE and leaves 8 and 11 unmarked; Calif puts the start at OpenJDK 17.0.6.

Runtime Listed as affected Source
OpenJDK 17, 21, 25 and 27 lines (not 8 or 11) OpenJDK advisory
Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 Oracle advisory
Oracle GraalVM GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; GraalVM Enterprise 21.3.20.0.3 Oracle advisory
OpenJDK-based builds Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK Calif

Fixed builds for the vendor distributions are being released by each vendor, so match on the vendor's advisory rather than the OpenJDK version string.

Does the processor matter?

For code execution, yes. Calif says Java4Shell "requires an x86-64 processor with AVX-512 VBMI support" and that ARM64 is not affected. It names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen Zen 4 or newer. Its Linux check: the flags line in /proc/cpuinfo must include avx512f, avx512bw, avx512vbmi and bmi2.

Check each host rather than assuming by server model or cloud instance type, since hypervisors can mask CPU features and node pools mix hardware. A host that fails the check today can pass it after a hardware refresh or a cloud migration, so it stays on the patch list either way.

The input path is the third condition. Oracle's note for this CVE says it "can only be exploited by supplying data to APIs in the specified Component," for example "through a web service." SentinelOne, quoted by Help Net Security, lists HTTP Basic credentials, SAML artifacts and CSRF tokens as carriers, and Calif describes a client-side exploit against a Java program that opens a TLS connection to a malicious server. Ruling out a Base64 path is harder than it sounds.

Where is the Java you can't see?

Inside other products. CISA's alert says JDKs and Java runtimes "may not appear as separate entries in software inventories," and points to runtimes bundled with third-party applications, container images and appliances.

When an application ships its own runtime, patching the system JDK changes nothing for that application; the fix comes as a new build from its vendor. Container images carry their runtime in a base layer, so the fix is a rebuild and redeploy. If your programs keep software bills of materials, a search for JDK components finds these faster than a host scan; our SBOM post covers those inventories.

From our delivery teams: On each application host, record the path of the java binary the running process actually uses, not just what java -version returns from the shell. They often differ, and the ticket should close on the one the service runs.

What if you can't patch today?

Calif lists two startup flags. -XX:-UseBASE64Intrinsics turns off hardware-accelerated Base64 encoding and decoding and is the narrower change. -XX:UseAVX=2 turns off AVX-512 entirely; Calif warns that OpenJDK on ARM doesn't recognize it and will fail to start, so keep it out of startup scripts shared with ARM hosts. Either flag works only after a restart and only for the JVMs it reaches, including bundled ones. Test before a production rollout.

CISA's interim controls are input-side: restrict and validate Base64 at the application boundary, enforce input-size limits and limit unauthenticated access. It also asks defenders to watch for rogue runtimes, unexpected JVM crashes and suspicious Java processes. VulnCheck found, per Help Net Security, that crashing an affected JVM is trivial and repeated requests can keep a service down, while code execution takes heap grooming and a separate memory leak. Treat unexplained JVM crashes on an exposed host as an incident, and consider rotating the secrets that host held.

How does BOD 26-04 treat it?

As of November 18, 2026, CVE-2026-114938 was not in CISA's Known Exploited Vulnerabilities (KEV) catalog, and the alert sets no date of its own. That doesn't leave agencies without a clock. Under Binding Operational Directive (BOD) 26-04, KEV status is one of four factors, with public exposure, automatability and technical impact, that set each asset's timeline, as our KEV catalog explainer describes. A KEV listing would change that calculation. Your CISO's office maps the directive's table to each system.

Help Net Security reported no evidence of successful attacks as of November 18. Calif says it is holding back product-specific exploit chains "until everyone has had a chance to upgrade" and will publish them later.

The patch order we'd use

Start with internet-facing hosts that meet all three conditions, beginning with identity and developer tools such as single sign-on, ticketing, artifact repositories and build servers. Next come Java clients and integrations that call outside servers, then internal hosts that meet all three, then everything else on an affected runtime.

For each host, keep the runtime vendor and build, the processor check result and the date of the patch or interim flag. Contractors running systems for an agency typically get timelines through their contract; ask the contracting officer or agency security office which applies.

The Bottom Line

Java4Shell is a patch-now flaw: crashing an affected JVM is easy even where code execution is hard. Sort hosts by runtime, processor and Base64 input path, patch the exposed internet-facing ones first, and chase the runtimes bundled inside applications and images. Our cybersecurity teams support federal programs on FISMA and NIST compliance.

FAQ

What is Java4Shell?

Java4Shell is the name Calif gave CVE-2026-114938, a memory corruption flaw in the x86-64 HotSpot Java Virtual Machine's Base64 decoder. CISA says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution. Oracle rates it 8.1 under CVSS 3.1, and Calif rates it 9.2 under CVSS 4.0.

Is Java 8 affected by Java4Shell?

The OpenJDK advisory of November 17, 2026 marks the 17, 21, 25 and 27 release lines for CVE-2026-114938, not 8 or 11. Oracle's advisory does list Oracle Java SE 8u511b33-perf, a separate Oracle build. Check the advisory from the vendor of the exact runtime you run.

Is Java4Shell being exploited?

Help Net Security reported on November 18, 2026 that there was no evidence of successful attacks yet, and CVE-2026-114938 was not in CISA's Known Exploited Vulnerabilities catalog as of that date. Calif is holding back its product-specific exploit chains until organizations have had time to upgrade.

Can I mitigate Java4Shell without patching?

Calif lists two interim startup options: -XX:-UseBASE64Intrinsics, which turns off hardware-accelerated Base64 encoding and decoding, or -XX:UseAVX=2, which turns off AVX-512 and should be used only on x86-64 hosts because OpenJDK on ARM fails to start with it. Either takes effect only after the JVM restarts. CISA also suggests validating Base64 input, enforcing size limits and limiting unauthenticated access until the patch is in.

Do contractors have to meet a deadline for Java4Shell?

CISA's alert urges patching but sets no date of its own, and the CVE had no KEV entry as of November 18, 2026. For agencies, BOD 26-04 sets timelines per asset from four risk factors, of which KEV status is one. Contractors running systems for an agency usually get timelines through their contract, so ask the contracting officer or agency security office which applies.

Sources

  1. CISA, Critical Java Vulnerability Requires Immediate Patching (November 17, 2026)
  2. Oracle, Critical Security Patch Update Advisory, November 2026 (November 17, 2026)
  3. OpenJDK, Vulnerability Advisory 2026/11/17
  4. CISA, Known Exploited Vulnerabilities Catalog, JSON data feed (checked November 18, 2026)
  5. Calif, Java4Shell (CVE-2026-114938) (November 17, 2026)
  6. Help Net Security, Java4Shell OpenJDK flaw, Exploitation is tricky and hinges on specific CPUs (November 18, 2026)

How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.

Yahia Aboushadi
About the author. Yahia Aboushadi is Director of Brand and Marketing at Pyramid Systems, an employee-owned federal IT firm in Fairfax, Virginia, that has delivered for federal agencies since 1995. . Connect on LinkedIn.

Continue reading

Related Insights

More from Pyramid Systems on federal cybersecurity.

Blue and gray network cables in a numbered patch panel, illustrating a post on the FBI ARTEX alert

Cybersecurity

17 November 2026
What the FBI ARTEX Alert Asks Federal Security Teams to Check

The FBI ARTEX alert says some intrusions reached privileged access in under three hours. Which systems it targets, what to check and the logs to have ready.

Read more
Several monitors showing green code above a desk in a dark room

Compliance

16 November 2026
What DoD Checks Before Granting a Continuous ATO (cATO)

Continuous ATO from the primary documents: DoD's three cATO competencies, what the evaluation criteria require, who approves, and civilian ongoing authorization.

Read more
Network equipment glowing green in a dark server room, the kind of cloud infrastructure the FedRAMP VDR/VER migration covers

Compliance

14 November 2026
FedRAMP VDR/VER Migration: The December Progress Report, Then Three 2027 Dates

FedRAMP's VDR/VER migration is due December 7, 2026. What NTC-0017 asks for in the progress report, and the 2027 dates that lead to remediation or revocation.

Read more
Several monitors showing code in a dim security workspace

Cybersecurity

13 November 2026
CISA's New Incident Reporting Form: What Changed on November 9, 2026

CISA's incident reporting form changed on November 9, 2026. What the new questions ask, who must report within one hour, and what to have ready before you file.

Read more