# Java4Shell: how to tell if your servers are exposed to the critical Java bug, and what to do

> Canada's Cyber Centre and CISA say patch now. The flaw only hits certain newer x86 chips, and there's a JVM flag to block it until you can update.

- Published: 2026-11-18T14:54:00.000Z
- By: The Circuit Staff
- Type: News
- Topics: Security
- URL: https://thecircuit.ca/posts/2026-11-18-java4shell-how-to-check/

The Canadian Centre for Cyber Security and the U.S. agency CISA are both telling organizations to patch "Java4Shell" (CVE-2026-114938) right away. It's a memory-corruption bug in the code Java uses to decode Base64 text, and an attacker can trigger it remotely without logging in. The [Cyber Centre's alert](https://cyber.gc.ca/en/alerts-advisories/al26-029-critical-vulnerability-impacting-oracle-java-cve-2026-114938) says it isn't aware of attacks yet, "but that can change quickly." [CISA's alert](https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching) credits the Canadian centre as a contributor.

Researchers at security firm Calif say they found the bug with an AI coding tool in about an hour. They've [published a test](https://calif.io/java4shell) that shows the memory overwrite, but they're holding back full attack code until people have had time to update.

## Are you exposed?

You need three things for this to matter:

- **A newer x86 processor with AVX-512 VBMI instructions.** That includes Intel Xeon chips from Ice Lake onward and AMD chips from Zen 4 onward, per Calif. ARM servers, including AWS Graviton and Apple silicon, aren't affected, [Endor Labs says](https://www.endorlabs.com/learn/java4shell-unauthenticated-rce-reported-in-openjdk-17-cve-2026-114938).
- **A recent Java runtime.** Endor says the flaw is in OpenJDK 17.0.6 and later, including Java 21, 25 and 27. Calif says builds based on OpenJDK are affected too, including Temurin, Corretto, Microsoft's, Zulu, Red Hat's and Oracle's own. Endor says Java 8 and 11 aren't affected, though Oracle's advisory lists a Java 8 build.
- **An app that decodes Base64 from outside.** That's common: logins, tokens and file uploads. Calif says it has working attacks against Keycloak, Jira, Confluence, Jenkins and Artifactory, among others.

To check a Linux server's processor, the Cyber Centre suggests `lscpu | grep avx512`. Endor's narrower check is `grep -o -w -m1 'avx512vbmi' /proc/cpuinfo`. Then find every Java install, including ones bundled inside vendor appliances and containers.

## What to do

1. **Patch.** Oracle fixed it in its November update. For other Java builds, follow your vendor's advisory. Endor warns that some of the public OpenJDK update branches didn't carry the fix yet as of Tuesday.
2. **If you can't patch yet,** start Java with `-XX:-UseBASE64Intrinsics`, or `-XX:UseAVX=2` as the Cyber Centre suggests. Both turn off the fast code path where the bug lives. VulnCheck [says both flags stopped the overflow](https://www.vulncheck.com/blog/java4shell) in its testing. Don't use the AVX flag on ARM machines: Java won't start.
3. **Prioritize internet-facing systems,** and check logs for crashes or odd activity. The Cyber Centre asks Canadian organizations that find signs of compromise to report them through its My Cyber Portal.

Crashing a vulnerable server is easy, VulnCheck says, but taking it over takes more work and depends on the app.

**Why it matters:** Java sits inside a huge amount of business software, often where nobody remembers putting it. The fix is simple, but the hard part is finding every copy of Java on your systems, so start that inventory today.
