GreyNoise had logged 192 Java4Shell-shaped requests from six IP addresses by 14:48 UTC on November 19, as scanning for the OpenJDK flaw continued. The threat-intelligence firm reported no successful intrusions on its monitoring sensors.

Its public tracker, last updated at 14:48 UTC on November 19, lists six source addresses and 192 requests. All six are classified as malicious, and the tracker shows zero confirmed successful intrusions against GreyNoise gridpoints. The addresses have requested application paths including Atlassian Jira endpoints and Spring Actuator.

SecurityWeek reported that WatchTowr’s honeypots had received blind exploit attempts, while Cloudflare observed a scanner return about 17 hours after an initial probe with the exploit trigger while impersonating Chrome. Previdian separately logged nine attempts from six IP addresses on November 18 and 19, but said its sensor data could not establish whether any target had been compromised.

The same report said VulnCheck had made a full remote-code-execution exploit available to its customers and that an Immersive researcher had developed a working exploit. Cisco’s product security team said it was aware of proof-of-concept code but had no knowledge of malicious use. The monitoring sources cited here have not confirmed a successful compromise.

Vendors are still mapping the vulnerability to their products. Siemens lists all versions of Industrial Edge Management Pro V1, Pro V2 and Industrial Edge Management Virtual as affected, with no fixes yet available. Cisco’s advisory lists more than a dozen affected products, while IOS XE and UCS Central remain under investigation; no workaround is available. Elastic says Elasticsearch 7.17.3 and later are affected, with authenticated access required for remote code execution and unauthenticated requests able to trigger denial of service. Logstash 8.6.2 and later can also be affected under a specific configuration, where untrusted input can cause a crash rather than code execution.

READ
Ukraine Detains Four in $40.5M Ransomware Probe

Red Hat has rated the issue Critical for RHEL 8, 9 and 10 and its OpenJDK 17, 21 and 25 builds, noting that the vulnerable code path is selected automatically on CPUs with AVX-512 VBMI support. Keycloak updated its container images after finding the flaw in versions 26.8.2-1 and 26.8.2-2; the 26.8.2-3 image includes a patched Java runtime. Atlassian is preparing fixes for its cloud and Data Center products, while Jenkins says controllers are at risk when they run vulnerable Java releases on affected CPUs.


Buy ExpressVPN with PayPal or Credit Card

Java4Shell, tracked as CVE-2026-114938, is a memory-corruption flaw in OpenJDK 17.0.6 and later, affecting its hardware-accelerated Base64 decoder. The vulnerable code path requires an x86-64 processor with AVX-512 VBMI support, so ARM-based systems are not affected. Oracle and OpenJDK released fixes on November 17, with patched builds including Java 17.0.21.1, 21.0.13.1 and 25.0.5.1, according to the OpenJDK vulnerability advisory and the Jenkins project. CISA has urged organizations to patch the flaw. Abijita’s earlier report explains the application-specific exposure conditions.

Advertisement