A new critical Java hole illustrates the enterprise IT visibility problem

When cybersecurity research firm Calif published details Tuesday of a potentially major Java security flaw, dubbed Java4Shell, it described an unauthenticated attacker’s ability to read Java heap memory, steal private keys, tokens, and session secrets, and reach remote code execution (RCE).

With Java being all-but-ubiquitous in today’s enterprise, coupled with the inability of CISOs to have visibility into every instance of it in their estate, this means that the bug could be a big problem for IT.

Java, which has had its fair share of cybersecurity issues lately, is well-known for safely handling memory. That is why a Java bug affecting memory management is so dangerous. Java4Shell, tracked as CVE-2026-114938, is a vulnerability in the OpenJDK x86-64 Base64 decoder that scores 9.2 in severity (Critical) under CVSS 4.0, Calif said. Oracle assigned it a lower rating of 8.1 (High) using CVSS 3.1.

Calif explained in its post describing the issue that Base64 is a common way of representing binary data as text. “It is used in authentication protocols, to encode file uploads, and to deliver network messages,” it wrote. “To decode Base64 faster, OpenJDK uses specialized x86-64 CPU instructions to process many bytes at once. We discovered a bug in optimized machine-level code that lets malformed input overwrite neighboring memory. With careful exploitation, the corruption can reveal sensitive memory, as Heartbleed did, or lead to remote code execution.”

It said that the corruption can be triggered by a string of just 64 “A” characters followed by a single equals sign (=); in older OpenJDK 17 versions, 128 “A” characters are required before the equals sign.

“Memory corruption is the most common class of vulnerability on the internet,” Calif said. “But one of Java’s biggest selling points is memory safety. Java manages memory on developers’ behalf and checks memory accesses, protecting applications from the memory-corruption bugs common in other software. But like PHP and many other technologies, much of Java itself is written in low-level languages like C, C++, and, in this case, assembly, where memory corruption is still a part of life.”

Assessing the bug’s potential for exploit is complicated because triggering it requires a hardware accelerated decoding function that’s used on some x86-64 processors supporting AVX-512 VBMI instructions. And fixing it requires patches from a lengthy list of vendors; just installing Tuesday’s patch from Oracle, which owns Java, is not going to do the trick.

Potential damage ‘extreme’

Noah Kenney, principal consultant at Digital 520, said the potential damage from an unpatched instance of exposed Java is extreme.

“The researchers were able to read Java heap memory before they achieved code execution, so an attacker may be able to steal tokens, credentials, or keys from those systems. That access can remain useful even after the vulnerable server has been patched,” Kenney said. “Any unexplained crashes on an exposed system should lead to a review of what secrets were in memory and whether they need to be rotated.”

But not every instance is vulnerable to this flaw. 

“The same Java application and version can be vulnerable on a newer x86 server and unaffected on older hardware because the faulty decoder only runs when AVX-512 is available,” he noted. “That makes a normal software inventory less useful than it usually is. CISOs need to know the Java distribution and version, the processor underneath it, and whether untrusted Base64 reaches the decoder. Installing a newer processor can expose an application that was safe on the server it replaced, without changing the application at all.”

A further complication is that enterprises will also be running Java from a massive array of specialized vendors.

“Oracle released a fix for its Java builds, but enterprises also run Java from Amazon, Eclipse, Microsoft, Red Hat, and Azul, along with runtimes buried inside commercial products and containers,” Kenney pointed out. “CISOs should start with identity systems and software-delivery infrastructure, identify the runtime each one is actually using, apply the appropriate vendor fix, and restart or rebuild the workload.”

He also said that outbound connections need to be evaluated. “Researchers demonstrated that a Java program could be compromised by connecting to a malicious TLS server, even when it had no service exposed to the internet.”

Aman Mahapatra, chief strategy officer for New York City-based technology consulting firm Tribeca Softech, agreed, pointing out, “the client-side exploit puts any Java process that connects to a malicious TLS server at risk: integrations, connectors, crawlers and batch jobs. Patch scopes built around internet-facing listeners will miss them.”

Lack of visibility a big problem

Mahapatra also stressed that many Java implementations can be hard to locate. 

“Your SBOM [software bill of

[…]
Content was trimmed to protect the source. Please visit the original article for the full text.

This article has been indexed from InfoWorld