Skip to main content

CISA Escalates Urgency on “Java4Shell” Flaw We Flagged Yesterday (CVE-2026-114938)

Scope: OpenJDK 17.0.6 and later, Oracle Java, and all major Java distributions built from the same code**

Severity: Amber

We covered Java4Shell in yesterday’s advisory as a critical flaw affecting the shared Java runtime behind Jenkins, Jira, Confluence, and Keycloak. CISA has since issued its own formal guidance urging organisations to patch immediately, confirming the technical details of the flaw: specially crafted Base64 input processed by the Base64 decoder in the x86-64 HotSpot Java Virtual Machine can crash the JVM entirely or, under certain conditions, lead to unauthenticated remote code execution. CISA specifically noted the flaw is reachable through ordinary application code paths, including a local Spring Boot application using Spring Security, underlining that this is not a theoretical or deeply obscure attack surface but one that sits in commonly deployed application frameworks. As of this writing there remains no confirmed evidence of active exploitation in the wild, but CISA’s decision to issue urgent guidance ahead of confirmed exploitation reflects how severe and how broadly reachable this flaw is judged to be. Patches are available from both Oracle and the OpenJDK project. If your organisation has not yet patched Java following yesterday’s advisory, treat this as today’s immediate priority rather than something to schedule for later in the week.

The Uganda National CERT and Coordination Center (CERT.UG/CC) encourages users and administrators to review the recommendations and apply the necessary updates.