A new critical Java hole illustrates the enterprise IT visibility problem
CSO Online ·

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 materials] can’t see the real exposure. Whether a service is vulnerable depends on the silicon underneath as much as the JDK version,” he said. “The same container image is exploitable on an Ice Lake or Zen 4 node and safe on ARM or older hardware, and autoscaling can move it between the two. For once, the organizations that refreshed their hardware are the exposed ones.” But it is the lack of visibility that concerns practitioners the most. The Java hole “exposes a blind spot in how enterprises identify, prioritize and validate vulnerabilities,” said Raj Annaladasu , staff customer success engineer at Palo Alto Networks. “Enterprise teams invest heavily in application code review, dependency scanning, and secure coding practices. Java4Shell is a reminder that vulnerabilities can originate below the application layer, inside the managed runtime itself.” “This is an important distinction: Java’s memory-safety abstractions do not protect an application from memory corruption originating inside a vulnerable native runtime implementation,” he said. “Applications may be using a standard Java API correctly while the underlying runtime implementation is vulnerable. This shifts the security boundary beyond application code and third-party dependencies to include the runtime, its implementation, and the hardware capabilities that influence execution.” This means, he said, that exploitability depends on multiple conditions coming together: an affected Java runtime, the relevant CPU instruction capabilities, the vulnerable execution path being enabled, and attacker-controlled input reaching the decoder. But, he pointed out, “one of the bigger challenges is discovering where Java is actually running. Runtime installations are often bundled inside third-party products, container images, appliances, custom runtime distributions, and application-specific directories. They may not appear as distinct entries in conventional software inventories. A clean application dependency scan or CMDB does not establish that the environment is free of vulnerable Java runtimes.” Java hides everywhere Given that there are going to be so many Java vendors, and so many hidden apps, at issue, the risk of a CISO missing a few is massive, noted Frank Dickson , principal analyst at Dickson Research. “Java4Shell is a big deal because a single missed server with Java is all an attacker needs, allowing someone who never logs in to read its memory, including personal data, private keys, and tokens,” he said. “From there, the attacker can run code on the server. If that server is an identity system like Keycloak or PingFederate, the attacker now owns you.” And, he said, it’s highly unlikely that enterprise CISOs will catch all or most Java instances. “Will a CISO miss one? The odds say yes. Java hides everywhere. Each Java instance needs its own fix,” Dickson said. Its popularity is Java’s greatest weakness Brian Levine , a partner with consulting firm Control Risks, said Java’s popularity is its biggest weakness. “Java runs the back office of corporate America: logins, code pipelines, ticketing, internal wikis,” he said. “Java4Shell lets an attacker who hasn’t even logged in take over some of the most sensitive of those systems by sending a short string of text. If your company runs Java on modern servers, and almost every large company does, you’re exposed until you patch.” He enumerated some examples: “Keycloak and PingFederate control who gets into your company. Jenkins and Artifactory build and store the software you ship. Jira and Confluence hold your roadmaps, incident notes and plenty of passwords people shouldn’t have pasted there,” he said. “Take over those and you aren’t breaking into one room. You’ve stolen the master key, the blueprints and the security guard’s notebook in one move.” He added, “Java programs that simply connect out to the wrong server can be compromised too. That last one means firewalls and perimeter controls don’t fully protect you.” However, he pointed out, “there’s one small mercy: the bug only fires on certain newer Intel and AMD chips. The catch is that those chips fill modern data centers and cloud fleets.”