Critical Java Security Flaw Could Let Hackers Take Control of Enterprise Applications

Oracle and the OpenJDK project have released security updates for a serious Java vulnerability that could allow attackers to execute malicious code on affected enterprise systems without logging in. The flaw, tracked as CVE-2026-114938, was disclosed on November 17 and prompted CISA to urge organizations to patch immediately.

Discovered by researchers at cybersecurity firm Calif, the vulnerability affects Java’s Base64 decoder, a component that converts encoded data back into its original form. The bug can corrupt computer memory, potentially causing applications to crash, exposing sensitive information or allowing attackers to execute code remotely.

Oracle addressed the issue in its November security update, while the OpenJDK project also released fixes for affected versions.

How serious is the vulnerability?

Oracle assigned the flaw a severity score of 8.1 out of 10, while Calif rated it 9.2 using a newer version of the industry-standard vulnerability scoring system. Although the scores are not directly comparable, both indicate a significant security risk.

The research published by Calif demonstrated that attackers could exploit the flaw to execute code without authentication on affected installations of popular enterprise applications, including Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.

These attacks were demonstrated using default application configurations on vulnerable Java systems. However, that does not mean every installation of these products is exposed. Successful exploitation requires a particular combination of software, processor capabilities and application behavior.

Researchers have also demonstrated how the vulnerability could expose sensitive information stored in application memory, including passwords and authentication tokens.

Which systems are affected?

The vulnerability is tied to a hardware-accelerated method of decoding Base64 data that Java uses to improve performance on certain processors.

It affects specific Intel and AMD processors supporting the AVX-512 VBMI instruction set, including some modern server and workstation processors. Systems using ARM64 processors are not affected.

The flaw is present in certain OpenJDK releases starting with Java 17.0.6, as well as affected builds of Java 21, 25 and 27. A specialized performance build of Java 8 is also vulnerable.

Even on an affected system, an attacker must be able to send specially crafted data to an application that passes it through the vulnerable decoding function. This can happen through everyday features such as authentication requests, file uploads or other network communications.

The vulnerability also requires an attack tailored to the targeted application, rather than a single technique that works against every Java system.

These conditions limit its reach. Most home users are unlikely to be affected, while organizations running Java-based enterprise applications, particularly those accessible over the internet, face a greater risk.

As of November 18, researchers had reported attempts to exploit the vulnerability, but no successful attacks had been publicly confirmed.

What should organizations do?

Organizations running affected Java versions should install the security updates released on November 17 or obtain the appropriate fixes from their Java vendors.

Administrators should also verify which Java version each application actually uses. Some enterprise products bundle their own Java runtimes, meaning that updating Java on a server may not protect applications still running an older, vulnerable version.

Internet-facing services should receive priority, especially those that process Base64 data submitted by remote users.

For systems that cannot be patched immediately, Calif’s researchers have documented temporary configuration changes that disable the vulnerable hardware-accelerated decoding feature. These workarounds should be tested carefully, as they can affect performance and do not replace installing security updates.

Organizations should also monitor for unusual application crashes, suspicious Java processes and other signs of attempted exploitation.

Although the flaw affects a relatively specific combination of hardware and software, its potential consequences remain serious. Installing the available fixes is the most reliable way to protect vulnerable Java systems.