Skip to content

Vulnerabilities & Patches

GreyNoise WatchTowr and Cloudflare observe Java4Shell scanning as vendors issue advisories

GreyNoise saw more than 150 Java4Shell-shaped requests from five IP addresses by early Nov. 19, while Cisco, Elastic, Red Hat and Keycloak disclosed affected products.

https://breach-signal.com/vulnerabilities/java4shell-openjdk-cve-2026-114938-vendor-advisories/

Share

Key facts

  • GreyNoise said that by early November 19 it had seen more than 150 Java4Shell-shaped requests from five IP addresses.
  • WatchTowr said attackers hit its global honeypot network and sprayed the internet with requests carrying ‘java4shell-recon' User-Agents, along with blind exploitation attempts built from correctly shaped requests.
  • Knott said attackers are expected to go product by product to improve exploits and make them more reliable for specific targets over the coming days.
  • Knott said that is where real exploitation starts to happen.

SecurityWeek reported on Nov. 19, 2026 that researchers at GreyNoise, WatchTowr and Cloudflare observed active scanning and exploitation probing for Java4Shell as vendors rushed out advisories for CVE-2026-114938.

GreyNoise said it saw more than 150 Java4Shell-shaped requests from five IP addresses by early Nov. 19, and the firm said it has not seen any successful intrusions on its sensors. WatchTowr said attackers hit its global honeypot network, a set of decoy systems designed to attract attacks, and sprayed the internet with requests carrying ‘java4shell-recon’ User-Agents, the browser identifiers sent with web requests, along with blind exploitation attempts built from correctly shaped requests.

Cloudflare’s Cloudforce One team said people scanning for the flaw are beginning to hide the tools they use. In one instance, an IP address probed a target using a Java4Shell-referencing user agent, then came back about 17 hours later with the exploit trigger while pretending to be Chrome. Cloudforce One also said on Nov. 18 that an IP address connected to Artex and Java4Shell activity appeared for the first time; Artex is a penetration testing framework built on open source AI that threat actors abuse to automate intrusions.

Previdian reported that its sensors recorded nine exploitation attempts from six IP addresses on Nov. 18 and 19, though its sensor data cannot confirm whether any targets were compromised. Calif disclosed the vulnerability on Nov. 17, the same day Oracle and the OpenJDK project issued patches. Java4Shell, tracked as CVE-2026-114938, is a memory corruption issue, a flaw that lets attackers manipulate program memory, in how OpenJDK 17.0.6 and later versions handle Base64 data.

The flaw requires an x86-64 processor with AVX-512 VBMI support, which newer Intel and AMD CPUs provide; the flaw does not affect ARM-based systems. AVX-512 VBMI is a CPU instruction-set feature for vector manipulation.

Calif claimed that attackers can achieve unauthenticated remote code execution on standard Jenkins, Jira, Confluence and Keycloak configurations, among other enterprise applications. No single exploit works against all of them, Calif said, because each requires a tailored attack chain. Calif’s proof-of-concept only triggers the memory corruption.

Cisco said it knows of proof-of-concept code but has seen no malicious use. The company confirmed that more than a dozen products carry the flaw, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance and Intersight Virtual Appliance. The company has not released fixes and says there are no workarounds, and it is still looking into whether IOS XE and UCS Central are affected.

Siemens said three Industrial Edge Management products carry the flaw and is developing patches, telling customers to take these instances offline until fixes are ready. Elastic said the flaw affects every Elasticsearch release from 7.17.3 onward. Remote code execution in Elasticsearch requires valid credentials with read permissions or higher, while denial-of-service, crashing or disabling a service, can occur without authentication.

Versions of Logstash from 8.6.2 onward are affected, but exploitation needs a specific configuration and results only in a crash. Elastic said fixes are coming in upcoming releases, and it has issued a hotfix for Elastic Cloud Serverless while changing the configuration for Elastic Cloud Hosted. Elastic said only a small number of Elastic Cloud Hosted deployments run on vulnerable CPUs.

Red Hat called the issue Critical, saying its RHEL versions 8, 9 and 10 and OpenJDK 17, 21 and 25 builds carry the flaw. Red Hat said the flaw exposes systems by default because the accelerated code path picks itself automatically on processors that report AVX-512 VBMI support, requiring no special configuration or non-default features, and Red Hat said it is speeding up patches. Keycloak said container images 26.8.2-1 and 26.8.2-2 included a vulnerable OpenJDK 21 build, then said on Nov. 19 that updated images carrying a patched Java runtime are release 26.8.2-3.

Atlassian said cloud customers do not need to take action because it handles the issue in cloud products. For Data Center products, Atlassian said customers should disable AVX-512 support until patches arrive for recent Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management installations. Jenkins said controllers face risk only when running vulnerable Java 17, 21 or 25 releases on CPUs with AVX-512 VBMI support, and the project advises updating to the November Java releases and then restarting Jenkins. Jenkins also has workarounds available.

Amazon, Microsoft and Azul have released patched OpenJDK distributions. VulnCheck has made a full remote code execution exploit available to its customers, and Immersive’s Kevin Breen said he has developed a working exploit.

Jake Knott, head of threat intelligence at WatchTowr, said what WatchTowr is seeing so far is not particularly functional or scary, but attackers want to leverage this vulnerability. Knott said attackers are expected to go product by product to improve exploits and make them more reliable for specific targets over the coming days, and that is where real exploitation starts to happen. “it shows the clear signal that attackers want to leverage this vulnerability,” Knott said.

Patch availability varies by vendor. Cisco has not released fixes and says there are no workarounds for its affected products. Red Hat said it is speeding up patches for RHEL versions 8, 9 and 10 and its OpenJDK 17, 21 and 25 builds. Keycloak released patched images as release 26.8.2-3 on Nov. 19, and Elastic has issued a hotfix for Elastic Cloud Serverless while changing the configuration for Elastic Cloud Hosted.

For products without fixes, vendors suggest interim steps. Siemens recommends taking its three affected Industrial Edge Management instances offline while it develops patches. Atlassian said Data Center customers should disable AVX-512 support until patches arrive for recent Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management installations.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *