On November 17, the U.S. Cybersecurity and Infrastructure Security Agency, or CISA, issued an alert urging organizations to immediately patch a Java vulnerability tracked as CVE-2026-114938. CISA calls the bug “Java4Shell” and describes it as a critical memory-corruption flaw in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine, which is part of the Java Development Kit. Specially crafted input, the alert says, could crash the JVM and allow unauthenticated remote code execution — meaning an attacker might run their own code without first logging in.

Java is a programming language and a runtime, a hidden engine that many websites, school tools, and company apps rely on even when users never see the name. CISA warns that Java runtimes may be bundled into third-party applications, container images, and appliances, and may not show up as their own line in a software inventory. That makes the first job identifying where Java is installed at all, then applying vendor patches, with internet-facing systems first in line.

If a patch cannot be applied right away, CISA recommends temporary defenses, including tighter checks on untrusted input and reduced unauthenticated access. Organizations should also review Oracle’s November 2026 security advisory and watch for odd signs, including unexpected Java crashes or suspicious Java processes. The Canadian Centre for Cyber Security contributed to the alert.

CERT-EU, the European Union’s computer emergency team, published a related advisory on November 18. It lists affected Oracle Java and OpenJDK versions, including ranges in Java 17, 21, 25, and 27, and says the bug is reachable only under certain hardware conditions on some x86-64 processors. ARM-based systems, CERT-EU says, are not affected. It assigned a CVSS score of 8.1. The same advisory describes a temporary vendor-documented setting that can turn off the vulnerable speed-up until a patch is installed, which requires a restart.

The Verge reported that researchers at a group called Calif found the bug with the help of AI, and that Oracle released a patch. A Docker blog post dated November 19 said OpenJDK and Oracle disclosed the issue on November 17, and that as of November 18 there were no public reports of exploitation in the wild. Docker also said researchers had demonstrated the risk against several widely used Java apps, but noted there is no single universal method and that demonstration details were not published.

The practical advice from the official alerts is simple, even if the bug is technical: find every Java runtime you depend on, including the ones tucked inside other products, and update them. Home users who never installed Java themselves may still have it inside an application, which is why vendors, schools, and IT teams are the main audience for the CISA alert.