Guide
CISA's Java4Shell alert: what is affected, how fast to patch, and the same-day KEV addition
What CISA's November 17, 2026 Java4Shell alert covers, how fast it says to patch, and why that day's KEV addition is a separate Puppet flaw.
What CISA's November 17 alert covers
CISA published an alert on November 17, 2026, that urges organizations to immediately patch an Oracle Java vulnerability tracked as CVE-2026-114938.
The alert calls the issue "Java4Shell." It describes it as a critical memory-corruption bug in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine, which ships as part of the Java Development Kit.
The alert says the flaw could have two effects. Specially crafted Base64 input could crash the JVM, and it could also let an attacker who has not authenticated run code remotely.
The flaw sits in a decoding routine inside the runtime, not in a single product.
What is affected, and why it may be hard to find
CISA's alert names the affected component, the HotSpot JVM on x86-64. It does not list version numbers and sends readers to Oracle for that detail.
The vendor document CISA points to is Oracle's Critical Security Patch Update for November 2026.
The first action CISA lists is to identify affected Java installations, and it sets a wide search scope. That scope covers JDKs and Java runtimes, including copies bundled with third-party applications or packaged inside container images and appliances.
CISA adds a note that inventories may not show everything, because JDKs and Java runtimes may not appear as separate entries.
The scoping work therefore has two parts. The first is checking installed versions against Oracle's security advisory, which CISA says gives the affected products and versions. The second is finding the runtimes that sit inside other products, images and appliances, where a standard inventory entry may not exist.
How urgently CISA says to patch
The alert states its timing as a call to patch immediately. It tells organizations to apply Java and vendor patches as soon as they are available and to start with internet-facing systems.
The alert's title, its "immediately" wording and its focus on internet-facing systems all express the same priority. The patch instruction covers both Java patches and vendor patches, which matches the bundled cases the alert raises in its inventory step.
CISA allows for systems that cannot be patched right away. For those, it lists temporary compensating controls, namely restricting and validating Base64 input at the application boundary, enforcing input-size limits, and limiting unauthenticated access.
The alert presents these controls as temporary measures for cases where immediate patching is not feasible.
CISA also asks defenders to watch for rogue runtimes, unexpected JVM crashes and suspicious Java processes.
The crash indicator ties back to the flaw itself, since CISA says crafted input could crash the JVM. The alert's list of things to watch for therefore includes the visible effect of the bug.
The same-day KEV addition is a different vulnerability
CISA issued a separate alert on November 17, 2026, announcing one addition to its Known Exploited Vulnerabilities catalog.
That single addition is CVE-2026-115731, a deserialization-of-untrusted-data flaw in Perforce Puppet Enterprise. The Java CVE is not the vulnerability added that day.
The KEV alert says CISA adds entries to the catalog when there is evidence of active exploitation. It lists the requirements for any potential addition as a CVE ID, evidence of exploitation and clear mitigation guidance.
The Java alert gives a different basis for its urgency. It rests on the nature of the flaw, which CISA labels critical and says could allow unauthenticated remote code execution.
The two documents answer different questions. The KEV alert reports a flaw CISA says is being exploited. The Java alert reports a flaw CISA says must be patched at once because of what it could allow. Neither document refers to the other, and the Puppet entry and the Java bug have different CVE numbers and different vendors.
What the KEV alert says about BOD 26-04
The KEV alert ties the catalog to Binding Operational Directive 26-04, which it says requires federal agencies to prioritize rapid remediation of high-risk vulnerabilities.
The alert defines the highest priority as KEV-listed CVEs on publicly exposed assets where exploitation grants total control of the asset, and it says the directive defers action on lower-risk flaws.
The alert says the directive also sets expectations for when agencies must check whether attackers compromised a system before the patch went on.
The directive binds only Federal Civilian Executive Branch agencies, but CISA urges all organizations to adopt risk-based vulnerability management and to prioritize KEV entries.
On the Puppet flaw, the KEV alert says this type of vulnerability is a frequent attack vector and a significant risk to the federal enterprise.
Reading the two alerts together
On November 17, 2026, CISA put two separate items in front of defenders. The first is the Java4Shell alert, CVE-2026-114938. Its scope is the x86-64 HotSpot JVM, and its timing instruction is "immediately," with patches applied as soon as Oracle and other vendors release them and internet-facing systems handled first.
The second is a KEV addition, CVE-2026-115731 in Perforce Puppet Enterprise. CISA added it on evidence of exploitation, and the KEV alert places it under the risk-based priorities of BOD 26-04.
The documents do not link the two flaws. They also say nothing about whether the Java CVE will join the catalog later. CISA's general statement is that it will keep adding vulnerabilities that meet its criteria.
Sources
By email, once a week
Get the week’s briefings on Friday
The week’s briefings and the new entries in CISA’s exploited-vulnerabilities catalog, in one email.
Unsubscribe any time.