Skip to main content

“Java4Shell” Flaw Reaches Jenkins, Jira, Confluence, and Keycloak Through a Shared Java Runtime (CVE-2026-114938)

Scope: OpenJDK 17.0.6 and later, and every major Java distribution built from it

Severity: Red

A critical vulnerability dubbed Java4Shell affects OpenJDK, the open-source implementation of Java that underpins an enormous share of enterprise software. The flaw, CVE-2026-114938, is a memory corruption bug in Java’s hardware-accelerated Base64 decoding function, a component used constantly across authentication flows, file uploads, and network communications. Because so many unrelated applications share the same underlying Java runtime rather than implementing their own Base64 handling, this single flaw reaches a strikingly wide range of major enterprise tools at once, including Jenkins, Atlassian Jira, Atlassian Confluence, and Keycloak, none of which share a common codebase beyond the Java platform itself. Researchers demonstrated that the memory corruption can be triggered trivially, with nothing more than 64 repeated “A” characters followed by a single equals sign, a payload simple enough to appear in many existing logs or fuzzing datasets without being recognised. The flaw affects OpenJDK 17.0.6 and later, along with every major commercial and community Java distribution built from the same code, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat OpenJDK. Organisations must update their Java runtime today across the board, and should specifically check applications that bundle their own private Java runtime rather than relying on the operating system’s version, since an OS-level update alone will not necessarily reach those.

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