TL;DR: Is your small business affected by the Java vulnerability Java4Shell?
The Java vulnerability called Java4Shell (CVE-2026-114938), made public on 17 November 2026, lets an attacker crash Java or take over its server with a short, malformed piece of Base64 text. It needs Java 17.0.6 or later on newer Intel or AMD chips; ARM chips are not affected. Cloud tools are your vendors' job. A server, Jira, Confluence, Keycloak login or Jenkins that you or your agency run needs Oracle's 17 November builds or the vendor's update, and a restart.
Developing story. Last updated 18 Nov 2026, 10:40 CET. We'll update this article as Oracle, OpenJDK and software vendors publish more.
Subject: Java4Shell (CVE-2026-114938): is our setup patched?
Hi [name],
Java4Shell, the Java vulnerability disclosed on 17 November, hits Java 17.0.6 and later on newer Intel and AMD chips. Please answer these by [day]:
1. Do any of our servers or tools run Java 17.0.6 or later on Intel Xeon Ice Lake or newer, or AMD Zen 4 or newer, chips?
2. Have you installed Oracle's 17 November builds (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1) or each product vendor's update?
3. Did you restart Java, and rebuild containers, afterwards?
4. Were internet-facing logins (Keycloak, Jira, Confluence, Jenkins) patched first?
5. Until a fix is in, have you set the temporary flag -XX:-UseBASE64Intrinsics, and will you remove it after patching?
Thanks,
[your name]
Building your first startup on a budget?
The Fe/male Switch startup game takes you from idea to first paying customers in weekly quests, with an AI co-founder and a community of founders.
👉 Start the game