Cybersecurity researchers have begun detecting attempts to exploit Java4Shell, a critical vulnerability affecting Java-based enterprise software, just days after its public disclosure.
Threat intelligence companies GreyNoise, WatchTowr, Cloudflare and Previdian have identified suspicious traffic associated with the flaw, tracked as CVE-2026-114938. The activity suggests attackers are searching for vulnerable systems, although there is no confirmed evidence of successful real-world compromises in the reports examined.
According to a 19 November report by SecurityWeek, GreyNoise recorded more than 150 requests matching the characteristics of a Java4Shell attack from five IP addresses by early Thursday. The company had not detected successful intrusions across its monitoring network.
The development follows the vulnerability’s disclosure by security firm Calif on 17 November, when Oracle and the OpenJDK project also released security fixes.
Attackers begin testing Java4Shell against internet-facing systems
WatchTowr reported suspicious requests reaching its global honeypot infrastructure, including traffic identifying itself through the java4shell-recon user-agent string.
The security company also observed attempts using request patterns associated with the vulnerability.
Jake Knott, WatchTowr’s head of threat intelligence, indicated that the early activity was not particularly sophisticated but demonstrated attackers’ interest in exploiting the flaw.
Researchers expect attempts to become more targeted as attackers investigate how different Java-based applications handle vulnerable input.
Cloudflare’s Cloudforce One team has observed a similar pattern, including efforts to conceal scanning activity.
In one case, an IP address initially used a user-agent string explicitly referencing Java4Shell. Approximately 17 hours later, the same address returned with an exploit-triggering request while presenting itself as Google’s Chrome browser.
Cloudflare also identified an IP address associated with both Java4Shell activity and Artex, an open-source AI penetration-testing framework that has reportedly been misused by threat actors.
Separately, Previdian recorded nine exploitation attempts originating from six IP addresses on 18 and 19 November. However, its monitoring data could not establish whether any targeted systems were compromised.
These observations demonstrate active probing and attempted exploitation, rather than confirmed successful attacks.
Cisco and Siemens confirm affected products
The emerging threat has prompted additional security advisories from major enterprise technology vendors.
Cisco confirmed that more than a dozen products are affected by Java4Shell, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance and Intersight Virtual Appliance.
At the time of SecurityWeek’s report, Cisco had not released fixes for the affected products and said no workarounds were available. The company was also investigating possible exposure in IOS XE and UCS Central.
Siemens identified three affected Industrial Edge Management products. While preparing security updates, the company advised customers to take vulnerable instances offline.
Red Hat classified the vulnerability as critical, confirming exposure in Red Hat Enterprise Linux 8, 9 and 10, alongside affected OpenJDK 17, 21 and 25 builds.
The company warned that vulnerable systems do not require unusual configurations because the affected hardware-accelerated decoding routine can be selected automatically on compatible processors.
Elasticsearch, Keycloak and Atlassian issue updates
Elastic confirmed that Elasticsearch versions from 7.17.3 onwards are affected.
According to the company, attackers require valid credentials with at least read permissions to achieve remote code execution. However, unauthenticated attackers may be able to trigger a denial-of-service condition.
Logstash 8.6.2 and later are also affected under specific configurations, although the reported impact is limited to application crashes.
Elastic has applied mitigations to its managed cloud services and is preparing additional product updates.
Meanwhile, Keycloak released updated container images on 19 November, including version 26.8.2-3, to replace earlier images containing a vulnerable OpenJDK runtime.
Atlassian said it was addressing the vulnerability in its cloud services without requiring action from cloud customers. For affected Data Center products, the company recommended disabling AVX-512 support while awaiting patches.
The Jenkins project also advised administrators running vulnerable Java versions on compatible processors to install updated runtimes and restart their controllers.
Java4Shell exploitation remains hardware-dependent
Java4Shell is a memory-corruption vulnerability in OpenJDK’s optimised Base64 decoder.
It affects certain Java installations running on x86-64 processors supporting AVX-512 VBMI instructions. ARM-based systems and processors lacking that capability are not vulnerable to this particular flaw.
Calif previously demonstrated unauthenticated remote code execution against several enterprise applications, including Jira, Confluence, Jenkins and Keycloak.
However, the researchers explained that exploitation requires application-specific techniques rather than a universal attack method.
SecurityWeek also reported that VulnCheck had developed a full remote-code-execution exploit for customers, while Immersive researcher Kevin Breen reported creating a working exploit.
Those developments establish that researchers have developed exploitation techniques, but they do not demonstrate that attackers have successfully compromised production systems.
Organisations urged to prioritise patching
The US Cybersecurity and Infrastructure Security Agency (CISA) has urged organisations to identify affected Java installations and apply available security updates.
Administrators should pay particular attention to enterprise applications containing bundled Java runtimes, as updating the operating system’s Java installation may not protect independently packaged software.
Where supported by the affected runtime, the JVM option -XX:-UseBASE64Intrinsics can temporarily disable the vulnerable optimised decoding routine. Product-specific vendor guidance should take precedence, particularly where no workaround has been approved.
With suspicious traffic already appearing across security monitoring networks and additional enterprise products confirmed vulnerable, organisations face increasing pressure to complete their assessments and deploy fixes before attackers develop more reliable, application-specific exploits.



