Malicious actors have begun targeting the recently disclosed Java4Shell vulnerability as new vendors publish security advisories detailing its impact on their products.
Tracked as CVE-2026-114938, Java4Shell is a memory corruption flaw related to how OpenJDK 17.0.6 and later versions process Base64-encoded data. Its exploitation requires an x86-64 processor supporting AVX-512 VBMI, a feature present in recent Intel and AMD CPUs. ARM-based systems are not affected.
Calif disclosed the flaw on November 17, the same day Oracle and the OpenJDK project released patches. Calif claims to have achieved unauthenticated remote code execution (RCE) against default configurations of Jira, Confluence, Jenkins, Keycloak, and other enterprise applications. They note that no single exploit works against all these products and that each requires a tailored attack chain.
Attackers probing vulnerable systems
As of the morning of November 19, threat intelligence firm GreyNoise had recorded over 150 requests matching the pattern of a Java4Shell attack from five IP addresses. It reported no successful intrusions on its sensors.
At WatchTowr, Jake Knott, Head of Threat Intelligence, describes similar activity: “We are already seeing attackers scanning the internet and hitting our global honeypot network with requests bearing ‘java4shell-recon’ User-Agents, as well as blind exploitation attempts using well-formed requests.” He adds: “What we’ve seen so far isn’t particularly functional or scary, but it clearly shows attackers want to exploit this vulnerability. In the coming days, we expect them to progress product by product to refine more reliable exploits, and that’s where real exploitation will begin.”
Cloudflare’s Cloudforce One team noted that the authors of these scans are beginning to conceal their tools. In one case, an IP probed a target with a user agent clearly referencing Java4Shell, then returned about 17 hours later with the exploit trigger, masquerading as the Chrome browser. On November 18, the same team observed for the first time an IP address used for both Artex and Java4Shell. Artex is an AI-powered open-source penetration testing framework that malicious actors are repurposing to automate intrusions.
For its part, Previdian reports that its sensors recorded nine exploitation attempts from six IP addresses on November 18 and 19, though it could not confirm if any targets were compromised. Cisco states it is aware of a proof-of-concept (PoC) exploit code but has no knowledge of it being used maliciously. The PoC published by Calif only triggers memory corruption, while VulnCheck has made a full remote code execution exploit available to its customers.
Vendors confirm impact, patches rolling out gradually
Cisco confirmed that more than a dozen of its products are affected, including Catalyst Center, Secure Network Analytics, Secure Workload, and Intersight Virtual Appliance. The group has not yet released patches and states there are no workarounds. Siemens, meanwhile, reports that three of its Industrial Edge Management products are impacted and recommends taking these instances offline pending the preparation of patches.
According to Elastic, all versions of Elasticsearch from 7.17.3 onward are affected. An attacker must have valid credentials with read or higher privileges to achieve remote code execution but can cause a denial of service without authentication. The company has deployed an emergency patch for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted, where only a small portion of deployments run on vulnerable processors.
Red Hat has rated the flaw as critical and indicates that RHEL 8, 9, and 10 are affected, as are its own builds of OpenJDK 17, 21, and 25. “No special configuration or non-default features are required. The accelerated code path is selected automatically as soon as the JVM runs on a processor reporting AVX-512 VBMI support, so affected systems are vulnerable upon installation,” the company writes, adding that patches are being expedited. Amazon, Microsoft, and Azul have released patched builds of their OpenJDK distributions, while Atlassian states its cloud products require no customer action.
