Skip to main content
Cybersecurity News Kinetic Potential

Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories

Threat actors have started targeting the recently disclosed Java4Shell vulnerability, as more vendors publish advisories detailing the flaw’s impact on their products.

Tracked as CVE-2026-114938, Java4Shell is a memory corruption bug in the way OpenJDK 17.0.6 and newer handle Base64 data. Exploitation requires an x86-64 processor supporting AVX-512 VBMI, a feature found in newer Intel and AMD CPUs. ARM-based systems are not affected.

Calif disclosed the bug on November 17, the same day Oracle and the OpenJDK project released patches.

Calif said it achieved unauthenticated remote code execution (RCE) against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications. However, it noted that no single exploit works against all of them, and that each needs a tailored attack chain.

Attackers are probing for vulnerable systems

As of early November 19, threat intelligence firm GreyNoise had recorded over 150 requests matching the shape of a Java4Shell attack, coming from five IP addresses. The company has not seen any successful intrusions on its sensors.

WatchTowr has also seen activity. “We are already seeing attackers spray the internet and hit our global honeypot network with requests decorated in ‘java4shell-recon’ User-Agents, alongside blind exploitation attempts using correctly shaped requests,” said Jake Knott, head of threat intelligence at WatchTowr.

“While what we’re seeing so far isn’t particularly functional or scary yet, it shows the clear signal that attackers want to leverage this vulnerability. Over the coming days, we expect attackers to iterate product-by-product to refine and build more reliable target-specific exploits, and that is where we start to see real exploitation happen,” Knott added.

Cloudflare’s Cloudforce One team has noticed that those scanning for the flaw are starting to conceal the tools they use. In one case, an IP address probed a target using a user agent that clearly referenced Java4Shell, then returned roughly 17 hours later with the exploit trigger while impersonating the Chrome browser.

On November 18, Cloudforce One also saw an IP address being used for both Artex and Java4Shell activity for the first time. Artex is an open source AI penetration testing framework that threat actors have been abusing to automate intrusions.

Threat intelligence firm Previdian says its sensors logged nine exploitation attempts from six IPs on November 18 and 19. However, it cautioned that its sensor data cannot confirm whether any targets were compromised.

Cisco’s product security team says it is aware of proof-of-concept (PoC) exploit code but has no knowledge of malicious use.

The PoC released by Calif only triggers the memory corruption. Meanwhile, VulnCheck has made a full RCE exploit available to its customers, and Immersive’s Kevin Breen has reported developing a working exploit.

Vendors confirm impact, but fixes are still rolling out

So far, Cisco has confirmed that more than a dozen of its products are affected, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance, and Intersight Virtual Appliance.

The networking giant has yet to release fixes and says there are no workarounds. It is still investigating whether IOS XE and UCS Central are impacted.

Siemens says three of its Industrial Edge Management products are affected. The company is working on patches and, in the meantime, recommends taking these instances offline.

According to Elastic, every Elasticsearch release from 7.17.3 onward is affected. Attackers need valid credentials with read permissions or higher to achieve RCE, but they can trigger a denial-of-service (DoS) condition without authentication.

Logstash 8.6.2 and later are also affected, although exploitation requires a specific configuration and can only cause a crash. Elastic plans to address the issue in upcoming releases.

The company has already deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted. It says only a small share of Elastic Cloud Hosted deployments run on vulnerable CPUs.

Red Hat has rated the issue Critical, saying that RHEL 8, 9 and 10 are affected, along with 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 whenever the JVM runs on a CPU reporting AVX-512 VBMI support, so affected systems are vulnerable out of the box,” Red Hat said, noting that patches are being fast-tracked.

The Keycloak team warned that its 26.8.2-1 and 26.8.2-2 container images bundled a vulnerable OpenJDK 21 build. On November 19, it announced updated images containing a patched Java runtime, including the 26.8.2-3 release.

Atlassian says it is working to address the issue in its cloud products, and that cloud customers do not need to take any action. For its Data Center products, until patches become available, Atlassian recommends disabling AVX-512 support as a workaround for the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center in standard installations.

The Jenkins project says controllers are only at risk if they run a vulnerable Java 17, 21 or 25 release on a CPU that supports AVX-512 VBMI. It advises users to update to the November Java releases and restart Jenkins. Workarounds are also available.

Among Java distributors, Amazon, Microsoft, and Azul have released patched builds of their OpenJDK distributions.

This article was published by Security Week. Please check their website for the original content.

Add new comment

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
1 + 4 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.