GreyNoise records over 150 Java4Shell attack-shaped requests

Previdian logged nine exploitation attempts from six IP addresses, while WatchTowr saw reconnaissance and blind attempts; the observations do not establish that a real target was compromised.
In this article
Attackers have begun probing for Java4Shell, a recently disclosed flaw in OpenJDK. As of early 19 November, threat intelligence firm GreyNoise had recorded more than 150 requests matching the shape of an attack from five IP addresses, but had seen no successful intrusions on its sensors. SecurityWeek reported the activity after Calif disclosed the flaw on 17 November, the same day Oracle and the OpenJDK project released patches.
Previdian said its sensors logged nine exploitation attempts from six IP addresses on 18 November and 19, but could not confirm whether any targets were compromised. WatchTowr also saw reconnaissance requests and blind exploitation attempts on its global honeypot network, which uses systems set up to attract and observe attackers. Its threat intelligence head, Jake Knott, said the activity observed so far was not particularly functional.
Earlier: Oracle releases patches for OpenJDK’s Java4Shell flaw
How the flaw can affect applications
Java4Shell, tracked as CVE-2026-114938, is a memory-corruption flaw in how OpenJDK 17.0.6 and newer handle Base64, a way of encoding data. Exploitation requires an x86-64 processor with AVX-512 VBMI support; ARM-based systems are not affected. The consequences depend on the application and its configuration.
Calif said its researchers ran code remotely without signing in against default configurations of several enterprise applications in tests. Each application required a tailored chain of steps; the demonstration Calif released publicly only triggers the memory corruption. Those tests are distinct from the later requests observed online.
Cloudflare’s Cloudforce One team saw one IP address probe a target while identifying its tool as related to Java4Shell, then return roughly 17 hours later with an exploit trigger while posing as the Chrome browser. Knott expects attackers to refine more reliable exploits for individual products over the coming days.
Vendor fixes and workarounds
Cisco said more than a dozen of its products are affected, with no fixes or workarounds yet available. It is still investigating IOS XE and UCS Central. Siemens said three Industrial Edge Management products are affected and recommended taking those instances offline while it works on patches.
Elastic said Elasticsearch releases from 7.17.3 onward are affected. Running code remotely requires valid credentials with at least read access, but an attacker can cause a denial of service—a disruption that makes a service unavailable—without signing in. Logstash 8.6.2 and later are also affected under a specific configuration, where exploitation can only cause a crash. Elastic plans fixes in upcoming releases; it has deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted.
Red Hat rated the issue critical and said RHEL 8, 9 and 10 and its OpenJDK 17, 21 and 25 builds are affected, and it is fast-tracking patches. The Keycloak team said images 26.8.2-1 and 26.8.2-2 included a vulnerable OpenJDK 21 build; on 19 November it announced updated images with a patched runtime, including 26.8.2-3.
Atlassian said cloud customers need take no action while it addresses the issue. Pending patches, it recommends disabling AVX-512 support for the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center in standard installations. The Jenkins project advises users of affected controllers to update to the November Java releases and restart Jenkins; controllers are at risk only if they run a vulnerable Java 17, 21 or 25 release on a processor supporting AVX-512 VBMI.
Checking Java builds
Adoptium listed the following fixed Eclipse Temurin builds and said it was publishing binaries as testing was completed. It recommends upgrading; administrators unable to do so immediately can temporarily disable the affected Base64 code path by adding -XX:-UseBASE64Intrinsics to the startup command.
| JDK | Fixed build |
|---|---|
| 27 | 27.0.1.1+4 |
| 25 | 25.0.5.1+2 |
| 21 | 21.0.13.1+2 |
| 17 | 17.0.21.1+2 |
Amazon, Microsoft and Azul have also released patched builds of their OpenJDK distributions.
Follow AveNews
SoftwareOracle releases patches for OpenJDK’s Java4Shell flaw
Oracle released patches for Java4Shell on 17 November. Calif says the flaw leaked and its researchers achieved remote code execution in tests. The firm rated it 9.2 and Oracle rated it 8.1 on different severity scales; Oracle had planned fixes for 11 Java vulnerabilities.
5 min
