Attackers are probing for Java4Shell, a newly disclosed Java vulnerability that can let them run code remotely on applications using particular x86-64 processors, SecurityWeek reported on November 19. Vendors are releasing patches and temporary protections, while some enterprise and industrial products still await fixes.
The vulnerability, CVE-2026-114938, affects OpenJDK’s Base64 decoder, which converts encoded data back into its original form. Red Hat’s bulletin rates the issue Critical and says exposure requires an affected Java runtime, a processor supporting AVX-512 VBMI instructions and an application that sends attacker-controlled Base64 data through the vulnerable decoder. ARM64 systems and x86-64 processors without that feature are not known to be affected.
Calif disclosed the flaw on November 17, the same day Oracle and the OpenJDK project released patches, SecurityWeek reported. Calif said it demonstrated unauthenticated remote code execution against default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications, but each application requires a tailored attack chain.
Probing is underway
By early November 19, GreyNoise had recorded more than 150 requests matching the shape of a Java4Shell attack from five IP addresses, without observing a successful intrusion on its sensors, SecurityWeek reported. WatchTowr also reported internet-wide probing, including requests carrying java4shell-recon User-Agent values and blind exploitation attempts with correctly shaped requests. Its threat intelligence chief, Jake Knott, described the activity as not yet particularly functional and anticipated attackers refining exploits for individual products.
Cloudflare’s Cloudforce One team observed one address return roughly 17 hours after an explicit Java4Shell probe, this time sending the exploit trigger while identifying itself as Chrome. On November 18, it also first observed an IP address associated with both Java4Shell activity and Artex, an open-source AI penetration-testing framework that threat actors have abused to automate intrusions.
Previdian recorded nine exploitation attempts from six IP addresses on November 18–19, though its sensors could not establish whether targets were compromised. Cisco’s product security team said it knew of proof-of-concept exploit code but had no knowledge of malicious use.
Calif’s public proof of concept triggers memory corruption rather than full code execution. SecurityWeek reported that VulnCheck had made a full remote-code-execution exploit available to customers and that Immersive researcher Kevin Breen had reported developing a working exploit.
Why hardware and application behavior matter
Red Hat identifies the vulnerable code in java.util.Base64.Decoder, in OpenJDK 17.0.6 and later, including Java 21 and 25. On eligible processors, the Java Virtual Machine—the runtime executing Java applications—automatically selects an accelerated decoder. Malformed input can corrupt memory and allow code execution within the Java process or crash the service.
An application can reach this decoder before checking a user’s identity. For example, HTTP Basic authentication credentials are Base64-encoded and may be decoded before authentication completes. Other possible inputs include SAML authentication artifacts, CSRF tokens used against forged requests and MIME-encoded words in messages.
Red Hat lists Intel Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4, Zen 5 and Zen 6 among relevant processor families. Exploitation also requires that the runtime has not already been restricted to -XX:UseAVX=2 or a lower AVX level.
Siemens’ November 18 advisory additionally specifies a JIT-compiled decoder, meaning one compiled into machine code during execution, and untrusted Base64 reaching Base64.getDecoded() or getUrlDecoded(). It classifies the flaw as a heap-based buffer overflow and assigns a CVSS severity score of 8.1.
Product scope matters when checking versions. Red Hat says its OpenJDK 8 and 11 builds lack the vulnerable code path. Siemens’ description separately lists affected Oracle Java SE versions 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and Oracle GraalVM Enterprise Edition 21.3.20.0.3. That description concerns data supplied to component APIs, such as through a web service, without requiring untrusted Java Web Start applications or applets.
Vendor exposure and patch status
Cisco’s advisory identifies 13 affected products. These include Catalyst Center, Smart PHY, Secure Workload, Smart Software Manager On-Prem, Native Broadband Network Gateway, Services as Code–Common Automation Framework, Ultra Cloud Core–Subscriber Microservices Infrastructure and Intersight Virtual Appliance, with fixed release numbers undetermined. Optical Network Planner is affected only in releases 26.4.1 and later, also with no fixed release number listed.
Cisco names prospective fixes for Connected Mobile Experiences 11.2, Secure Network Analytics 7.6.0, Cisco IQ Virtual Appliance v1.3.2 and Splunk AppDynamics On-Premises Virtual Appliance 27.1.0, but marks each as TBD. These are pending releases, not available patches. SecurityWeek reported that Cisco had no workarounds.
IOS XE and UCS Central remain under investigation. Cisco lists Catalyst SD-WAN Controller, Manager and Validator; Identity Services Engine; IOS XR; Nexus Dashboard; NX-OS; Secure Firewall ASA, FMC and FTD; and UCS Director as unaffected. Its investigation remains ongoing.
Siemens lists all versions of Industrial Edge Management Pro V1, Pro V2 and Virtual as affected, subject to the hardware and runtime conditions, with no fix available. Industrial Edge Device Kit does not include Java, and Industrial Edge Management Cloud runs on a different platform; both are listed as unaffected.
SecurityWeek reported additional vendor findings:
- Elastic: Elasticsearch 7.17.3 and later are affected. Remote code execution requires valid credentials with at least read permissions, while unauthenticated attackers can cause denial of service. Logstash 8.6.2 and later can crash only under a specific configuration. Fixes are planned for upcoming releases. Elastic has deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted; it says only a small share of Hosted deployments use vulnerable CPUs.
- Atlassian: Work is underway on cloud products, and cloud customers need take no action. Pending patches, Atlassian recommends disabling AVX-512 for the latest Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center versions in standard installations.
- Jenkins: Controllers are at risk only when a vulnerable Java 17, 21 or 25 runtime runs on an AVX-512 VBMI-capable CPU. The project advises updating to the November Java releases and restarting Jenkins; workarounds are also available.
- Upstream Keycloak: Container images 26.8.2-1 and 26.8.2-2 bundled vulnerable OpenJDK 21 builds. On November 19, the team announced updated images with patched Java runtimes, including 26.8.2-3.
- Java distributors: Amazon, Microsoft and Azul have released patched OpenJDK builds.
Red Hat directly lists RHEL 8, 9 and 10 and its OpenJDK 17, 21 and 25 builds as affected. Products supported on RHEL, including RHEL CoreOS, may also be impacted. That includes RHEL- or UBI-based containers and layered products such as OpenShift, OpenStack and Red Hat Virtualization that obtain packages through RHEL channels.
What administrators should do
Red Hat recommends inventorying each application’s Java vendor and full build version, including runtimes inside containers, appliances and product installations. Administrators can check Java with java -version and check Linux CPU support with grep -o avx512vbmi /proc/cpuinfo | head -1. Output containing avx512vbmi identifies the relevant instruction-set support.
Red Hat flags AWS C6i/M6i/R6i and C7i/M7i/R7a, GCP C3/C3D/C4/C4D/N4/N4D/M3/M4, and Azure Dsv5/Dsv6/Dasv6/Dasv7 and related D-series v5–v7 instances as cloud families worth checking. It prioritizes internet-facing applications and authentication services.
Until a permanent update is applied, Red Hat prefers starting affected runtimes with -XX:-UseBASE64Intrinsics, which disables only the accelerated Base64 implementation. Alternatively, -XX:UseAVX=2 disables AVX-512 entirely. The latter flag must be limited to x86-64: ARM64 runtimes do not recognize it and will fail to start. Neither flag is needed on ARM64 or processors without AVX-512 VBMI.
For Red Hat build of Keycloak, affected versions include 26.4 and 26.6 and later. Red Hat Single Sign-On 7.6 is affected only on OpenJDK 17; OpenJDK 11 deployments, including rh-sso-7/sso76-openshift-rhel8, are unaffected. Keycloak processes Base64 before authentication, so requiring a login does not protect an exposed instance.
Red Hat directs administrators to append -XX:-UseBASE64Intrinsics through JAVA_OPTS_APPEND and restart every Keycloak instance, including failover and rolling-update nodes. Preserve existing options. For managed services, set the variable in the service environment; an interactive shell export does not alter a running service. Container and Operator-managed deployments must pass it to every server container and replace or restart every pod.
The Keycloak Operator uses a separate runtime and needs JDK_JAVA_OPTIONS on its Deployment instead. Where Operator Lifecycle Manager controls it, persist the setting in the Subscription’s spec.config.env. Both the Operator and its managed Keycloak pods require their respective settings. Verify each running runtime with jcmd and VM.flags -all: UseBASE64Intrinsics should report false.
Siemens recommends blocking direct internet access to affected Industrial Edge Management installations, with shutdown or disabled internet connectivity as its most effective immediate measure until fixes are applied. Red Hat advises using supported vendor update paths for bundled runtimes, rebuilding customer containers after base-image updates and keeping underlying RHEL OpenJDK packages current. Apply permanent fixes when available, then remove the temporary flags.




