If your company runs Java-based systems on its own servers, such as Jira, Confluence, Jenkins or Keycloak, update Java on them this week. On 17 November 2026 Oracle and OpenJDK released a fix for a flaw named Java4Shell (CVE-2026-114938), scored 8.1 by Oracle and 9.2 out of 10 by the firm that found it. The US cyber agency CISA says crafted input could crash the program and allow remote code execution without any login. The fixed versions are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. If you cannot update today, a temporary setting closes the hole.
What exactly happened?
The flaw sits in the part of the Java virtual machine that decodes Base64, a common format for carrying data inside requests and login tokens. When it receives malformed data it writes over neighbouring memory, which can crash the application, expose secrets held in memory, or let an attacker run commands on the server.
Security firm Calif found it using AI tools. It says finding the bug took about one hour, and building the first working exploit took about two more, at a token cost under 200 dollars. The flaw heads Oracle's November security update, which carries 11 new fixes for Java SE.
Are your company's systems exposed?
Not every machine running Java is affected. Three conditions must all be true:
- Version: Java 17 from 17.0.6 onward, and every Java 21, 25 and 27 release before the fix, whether from Oracle, OpenJDK or a distribution built on it such as Corretto or Temurin.
- Processor: an x86-64 server with AVX-512 VBMI support, such as Intel Xeon from Ice Lake through Granite Rapids, or AMD EPYC or Ryzen from Zen 4 onward. ARM64 processors are not affected.
- Software: an application that decodes Base64 data coming from users, which is very common.
Calif demonstrated remote code execution before login, in default configurations, on Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and after login on Apache Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. It says the list is not exhaustive.
To check whether a server's processor is affected, your IT team can run this command, published by Calif, on Linux servers: grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'. If all four instructions appear in the output, the processor is the affected type; if one is missing, it is not affected by this flaw, although the Java update is still needed for the other flaws it fixes.
Has it been exploited yet?
So far there is no confirmed successful attack. Sophos says a public proof of concept exists and researchers have reported exploitation attempts. Now that the method is public, the gap between disclosure and real attacks is usually short, so do not wait for the first breach headline.
What to do this week
- Inventory every copy of Java: CISA recommends listing them all, including those bundled inside off-the-shelf software, Docker containers and appliances, because they may not show up in the list of installed programs.
- Start with what the internet can reach: your single sign-on portal, a Jira or Confluence open to clients, and any public API.
- Update Java to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, or your vendor's equivalent, then restart the application. If Java is bundled in a commercial product, ask the vendor for its update.
- If you cannot update today: start the application with
-XX:-UseBASE64Intrinsics, which disables the affected code, or-XX:UseAVX=2on x86-64 servers only. CISA also advises limiting unauthenticated access and capping input size. - Watch: any unexpected crash of a Java application or unknown Java process on a server deserves a look.
The Origami view
Many Saudi businesses do not know they run Java at all, because they bought Jira, a single sign-on system or a reporting tool, and Java is buried inside it. So the first step is not the update but the question: where does Java run here? We covered this risk in our article on enterprise Java platform flaws.
What stands out is that AI found a years-old flaw in three hours. Attackers have the same tools, so a monthly or quarterly patch cycle is no longer enough for systems exposed to the internet. If you need someone to inventory your systems and plan the update, the Origami team can help.
Conclusion
Ask your IT team two questions today: where does Java 17, 21, 25 or 27 run on our servers, and do those processors support AVX-512? If the answer is yes, update this week starting with internet-facing systems, and apply the temporary setting to anything you cannot update right away.
Sources
Frequently asked questions
How do I know if my company uses Java?
Ask your IT team which systems run on your servers, such as Jira, Confluence, Jenkins, Keycloak, Elasticsearch or any off-the-shelf business software. Many bundle their own Java, and the version shows with the command java -version.
Are staff computers at risk too?
The main risk is servers that receive data from the network. The flaw needs Java 17 or newer on a processor with AVX-512 VBMI, and ARM64 processors are not affected, so start with your servers.
Is there a workaround if I cannot update?
Yes. Start the Java application with -XX:-UseBASE64Intrinsics, which disables the affected code, or -XX:UseAVX=2 on x86-64 servers only, and restrict internet access to the application until you update.
We run Java 8 or 11. Are we safe?
Standard OpenJDK 8 and 11 are not listed for this flaw in the OpenJDK table, but Oracle lists the 8u511b33-perf build. The same update fixes other flaws in 8 and 11, so apply it anyway.







