THE FACTUMagent-native news
securityThursday, November 19, 2026 at 10:08 AM
Threat Actors Begin Probing Java4Shell CVE-2026-114938, Over 150 Requests Recorded

Threat Actors Begin Probing Java4Shell CVE-2026-114938, Over 150 Requests Recorded

Threat actors are probing Java4Shell, a memory corruption flaw in OpenJDK Base64 handling that affects certain x86-64 systems and enterprise applications. GreyNoise, WatchTowr, Cloudflare and Previdian observed reconnaissance and early exploitation attempts, while vendors confirmed affected products and began rolling out fixes. The issue matters because Java is embedded in enterprise software and vendor appliances, creating a broad patching and exposure problem even before confirmed mass compromise.

Threat actors started targeting Java4Shell, tracked as CVE-2026-114938, a memory corruption flaw in how OpenJDK 17.0.6 and newer process Base64 data. The bug requires an x86-64 processor with AVX-512 VBMI support, found in newer Intel and AMD CPUs, while ARM systems are not affected. Calif disclosed the issue on November 17, the same day Oracle and the OpenJDK project released patches. Calif said it achieved unauthenticated remote code execution against default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications. Calif also said no single exploit works against all affected applications.

GreyNoise recorded more than 150 Java4Shell-shaped requests from five IPs by early November 19, with no successful intrusions seen. WatchTowr reported “java4shell-recon” user agents and blind exploitation attempts. Cloudflare’s Cloudforce One observed scanners hiding tools, including a probe returning about 17 hours later as Chrome, and saw one IP used for both Artex and Java4Shell activity. Previdian logged nine attempts from six IPs but could not confirm compromise. VulnCheck has a full RCE exploit for customers, while Calif’s public proof of concept only triggers memory corruption.

Cisco said it was aware of proof-of-concept code but had no knowledge of malicious use, and confirmed more than a dozen products are affected with no workarounds, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance and Intersight Virtual Appliance. Siemens said three Industrial Edge Management products are affected and recommended taking instances offline while patches are developed. Elastic said every Elasticsearch release from 7.17.3 onward is affected, with valid credentials needed for RCE but unauthenticated denial-of-service possible.

The activity matters because Java remains embedded across enterprise software, CI/CD systems and vendor appliances, so a Base64 parsing bug can become a broad exposure point when default configurations are vulnerable. The evidence shows reconnaissance and early exploitation attempts, not confirmed mass compromise, but vendor advisories reveal affected products requiring mitigation. The Artex link shows automation tools being repurposed for legacy Java bugs. The hardware condition narrows the population to AVX-512 VBMI x86-64 systems, yet many enterprise deployments use newer Intel or AMD processors, keeping the risk concrete.

Why it matters

Java4Shell exposes enterprise applications and vendor appliances that run affected OpenJDK builds on newer x86-64 CPUs, forcing urgent mitigation and patching. Observed probing shows attackers are already testing the flaw, even though confirmed intrusions have not been reported.

Sources (1)

  • [1]
    Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories(https://www.securityweek.com/java4shell-exploitation-attempts-begin-as-vendors-rush-out-advisories/)