Executive Summary
In November 2026, security research firm Calif disclosed CVE-2026-114938, dubbed Java4Shell, a critical pre-authentication remote code execution vulnerability scoring 9.2 under CVSS 4.0. The flaw resides in Java's AVX-512 VBMI-accelerated Base64 decoder present in Java 17.0.6 and later on Intel and AMD x86-64 processors. Attackers can send a malformed Base64 string through unauthenticated HTTP paths such as login headers, SAML artifacts, and CSRF tokens to trigger an out-of-bounds memory write, ultimately enabling full JVM takeover. Jira, Confluence, Jenkins, Keycloak, JFrog Artifactory, and PingFederate are confirmed exploitable without credentials under default configurations. Oracle, Amazon Corretto, and Azul Zulu have released patches; Red Hat fixes remain pending as of disclosure.
Java4Shell represents a generational escalation in JVM-layer risk, targeting the runtime itself rather than application logic. With hundreds of millions of Java deployments worldwide and exploit primitives already partially reproduced by multiple independent labs, organizations running unpatched Java on modern Intel or AMD server hardware face imminent, unauthenticated takeover risk across their entire application stack.
Why This Matters Now
Java4Shell (CVE-2026-114938) is urgently critical because it enables unauthenticated remote code execution against six widely deployed enterprise platforms—Jira, Jenkins, Keycloak, Confluence, Artifactory, and PingFederate—simply by sending a malformed HTTP request. With partial exploits already publicly reproduced, Red Hat patches still pending, and no current CISA KEV listing masking the real risk, organizations must patch or apply JVM flags immediately to prevent full server compromise.
Attack Path Analysis
An unauthenticated attacker exploits CVE-2026-114938, a memory corruption flaw in Java's AVX-512-accelerated Base64 decoder, by sending malformed Base64 strings to pre-authentication endpoints in Jira, Jenkins, Keycloak, Confluence, JFrog Artifactory, or PingFederate, triggering an out-of-bounds write that enables remote code execution without any credentials. Once a foothold is established via arbitrary code execution on the JVM, the attacker escalates privileges within the application context, moves laterally across adjacent services sharing the same network segment, establishes outbound command-and-control channels, and ultimately exfiltrates sensitive data or deploys destructive payloads, with CNSF controls such as Inline IPS, Zero Trust Segmentation, East-West Traffic Security, Egress Security, and Multicloud Visibility providing layered opportunities to detect or block each stage.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
An unauthenticated remote attacker sends crafted HTTP requests containing malformed Base64-encoded strings (e.g., in Authorization headers, SAML artifacts, or CSRF tokens) to publicly accessible pre-auth endpoints of Java-based applications (Keycloak, Jira, Jenkins, Confluence, JFrog Artifactory, PingFederate) running on x86-64 AVX-512 VBMI-capable hosts. The malformed string triggers an out-of-bounds write in Java's AVX-512 Base64 decoder (CVE-2026-114938), which via heap memory manipulation (JavaBleed technique) achieves arbitrary code execution on the JVM without any authentication. The CNSF Inline IPS (Suricata) capability can detect and block known exploit payloads matching CVE signatures at the network layer; the Cloud Native Security Fabric (CNSF) with real-time inline enforcement provides a high-weight control at this stage.
Related CVEs
CVE-2026-114938
CVSS 8.1A heap buffer overflow in the AVX-512 VBMI-accelerated Base64 decoder in Java 17.0.6 and later (on x86-64 chips supporting AVX-512 VBMI) allows an unauthenticated remote attacker to cause a JVM crash or, in certain application environments, achieve arbitrary remote code execution prior to authentication by supplying a malformed Base64-encoded string.
Affected Products:
Oracle Java SE 17 – 17.0.6, 17.0.7, 17.0.8, 17.0.9, 17.0.10, 17.0.11, 17.0.12, 17.0.13, 17.0.14, 17.0.15, 17.0.16, 17.0.17, 17.0.18, 17.0.19, 17.0.20, 17.0.21.0.3
Oracle Java SE 21 – 21.0.13.0.3 and earlier
Oracle Java SE 25 – 25.0.5.0.3 and earlier
Oracle Java SE 27 – 27.0.1.0.3 and earlier
Oracle Java SE 8 Performance Pack – 8u511b33-perf
Oracle GraalVM for JDK 17 – 17.0.21.0.3 and earlier
Oracle GraalVM for JDK 21 – 21.0.13.0.3 and earlier
Oracle GraalVM Enterprise Edition – 21.3.20.0.3 and earlier
Amazon Corretto 17 – 17.0.6 through 17.0.21.1.1
Amazon Corretto 21 – affected builds prior to 21.0.13.1.2
Amazon Corretto 25 – affected builds prior to 25.0.5.1.2
Amazon Corretto 27 – affected builds prior to 27.0.1.1.4
Azul Zulu 17 – affected builds from 17.0.6 prior to 17.70.201
Azul Zulu 21 – affected builds prior to 21.54.201
Azul Zulu 25 – affected builds prior to 25.38.201
Azul Zulu 27 – affected builds prior to 27.30.201
Red Hat Red Hat Enterprise Linux 8, 9, 10 / OpenJDK 17, 21, 25 – 17.0.6 and later (no fix released as of disclosure date)
SAP SapMachine 17 – affected builds prior to 17.0.21.1
SAP SapMachine 21 – affected builds prior to 21.0.13.1
Atlassian Jira – versions bundling affected Java runtime
Atlassian Confluence – versions bundling affected Java runtime
Red Hat Keycloak – versions bundling affected Java runtime
JFrog Artifactory – versions bundling affected Java runtime
Jenkins Jenkins – versions bundling affected Java runtime
Ping Identity PingFederate – versions bundling affected Java runtime
Exploit Status:
proof of conceptReferences:
https://www.cve.org/CVERecord?id=CVE-2026-114938https://nvd.nist.gov/vuln/detail/CVE-2026-114938https://www.oracle.com/security-alerts/cspunov2026.htmlhttps://openjdk.org/groups/vulnerability/advisories/2026-11-17https://www.oracle.com/java/technologies/javase/17-0-21-1-relnotes.htmlhttps://explore.alas.aws.amazon.com/CVE-2026-114938.htmlhttps://access.redhat.com/security/vulnerabilities/RHSB-2026-018https://www.cyber.gc.ca/en/alerts-advisories/al26-029-critical-vulnerability-impacting-oracle-java-cve-2026-114938https://calif.io/java4shellhttps://www.upwind.io/blog/java4shell-what-we-know-now-and-what-comes-nexthttps://blackpointcyber.com/blog/java4shell-cve-2026-114938-java-base64-decoder-flaw/https://github.com/openjdk/jdk/pull/32781https://github.com/corretto/corretto-17/blob/develop/CHANGELOG.md
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Exploitation for Client Execution
Command and Scripting Interpreter
Exploitation for Defense Evasion
Access Token Manipulation
Data from Local System
Endpoint Denial of Service
Unsecured Credentials
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Timely Application of Security Patches
Control ID: Requirement 6.3.3
NYDFS 23 NYCRR 500 – Vulnerability Management and Incident Response
Control ID: Section 500.7 / 500.16
DORA (EU Digital Operational Resilience Act) – ICT Security Controls and Threat-Led Testing
Control ID: Article 9 / Article 10
NIS2 Directive – Vulnerability Handling and Incident Reporting
Control ID: Article 21(2)(e) / Article 23
CISA Zero Trust Maturity Model 2.0 – Application-Layer Threat Detection and Automated Remediation
Control ID: Application Pillar – Visibility & Analytics / Automation & Orchestration
ISO/IEC 27001:2022 – Management of Technical Vulnerabilities and Software Installation Controls
Control ID: Annex A 8.8 / Annex A 8.19
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Java4Shell CVE-2026-114938 enables pre-auth RCE across Jira, Jenkins, and Keycloak, critically exposing IT infrastructure running Java 17+ on AVX-512 x86-64 hardware, risking full JVM takeover without authentication.
Financial Services
Pre-auth RCE in Keycloak and PingFederate identity platforms threatens financial services authentication pipelines, with lateral movement and exfiltration risks mapped to PCI 4.0 and NIST 800-53 compliance frameworks.
Health Care / Life Sciences
Unauthenticated remote code execution via Base64-decoded SAML and HTTP headers in Keycloak and Jira endangers healthcare identity systems, violating HIPAA 164.312 controls for data integrity and transmission security.
Computer Software/Engineering
Jenkins and JFrog Artifactory exposure in software build pipelines enables supply chain compromise via pre-auth RCE, threatening CI/CD integrity with zero-trust segmentation and egress security controls critically undermined.
Sources
- Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and Morehttps://thehackernews.com/2026/11/java4shell-cve-2026-114938-enables-pre.htmlVerified
- Oracle Critical Patch Update November 2026 - Security Advisoryhttps://www.oracle.com/security-alerts/cspunov2026.htmlVerified
- OpenJDK Vulnerability Advisory 2026-11-17https://openjdk.org/groups/vulnerability/advisories/2026-11-17Verified
- Amazon Linux Security Advisory - CVE-2026-114938https://explore.alas.aws.amazon.com/CVE-2026-114938.htmlVerified
- Red Hat Security Bulletin RHSB-2026-018 - Java4Shellhttps://access.redhat.com/security/vulnerabilities/RHSB-2026-018Verified
- Canada's Cyber Centre Government Alert AL26-029 - Critical Vulnerability Impacting Oracle Java CVE-2026-114938https://www.cyber.gc.ca/en/alerts-advisories/al26-029-critical-vulnerability-impacting-oracle-java-cve-2026-114938Verified
- CVE-2026-114938 Official CVE Recordhttps://www.cve.org/CVERecord?id=CVE-2026-114938Verified
- Java4Shell (CVE-2026-114938): Technical Write-Up by Calif Security Researchhttps://calif.io/java4shellVerified
- Java4Shell: What We Know Now and What Comes Next - Upwind Security Lab Resultshttps://www.upwind.io/blog/java4shell-what-we-know-now-and-what-comes-nextVerified
- Java4Shell CVE-2026-114938 Java Base64 Decoder Flaw - Blackpoint Cyber Adversary Pursuit Grouphttps://blackpointcyber.com/blog/java4shell-cve-2026-114938-java-base64-decoder-flaw/Verified
- Oracle Java SE 17.0.21.1 Release Noteshttps://www.oracle.com/java/technologies/javase/17-0-21-1-relnotes.htmlVerified
- OpenJDK Pull Request 32781 - AVX-512 Base64 Decoder Overflow (Public Disclosure Precursor)https://github.com/openjdk/jdk/pull/32781Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant because CVE-2026-114938 targets pre-authentication endpoints across widely deployed Java-based services, giving an unauthenticated attacker an immediate foothold into cloud-hosted workloads. By enforcing inline inspection, workload segmentation, and controlled egress boundaries, the CNSF fabric would likely reduce the attacker's ability to move freely across services, establish outbound channels, or extract data at scale.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Inline inspection at the network layer would likely intercept crafted exploit payloads before they reach vulnerable application endpoints, reducing the probability that the malformed Base64 request successfully triggers the out-of-bounds write in the JVM decoder.
Control: Zero Trust Segmentation
Mitigation: Zero Trust Segmentation would likely constrain the scope of credentials and service identities reachable from a single compromised workload, reducing how far stolen tokens or cloud IAM credentials could be leveraged across the broader environment.
Control: East-West Traffic Security
Mitigation: East-West Traffic Security enforcement would likely reduce the attacker's ability to move freely between workloads, constraining lateral paths even when a valid token is presented from a compromised service identity.
Control: Multicloud Visibility & Control
Mitigation: Centralized traffic observability across cloud environments would likely surface anomalous outbound connection patterns from compromised application hosts, reducing the time the attacker can operate undetected while beaconing to external infrastructure.
Control: Egress Security & Policy Enforcement
Mitigation: Egress Security enforcement with FQDN-based filtering would likely constrain the attacker's ability to transfer data to unauthorized external destinations, reducing the volume and reach of a successful exfiltration attempt.
Residual impact would likely be scoped to workloads that were directly reachable before segmentation boundaries took effect, reducing the probability of environment-wide ransomware propagation or broad supply chain contamination — though localized disruption to identity, CI/CD, or collaboration services could still occur.
Impact at a Glance
Affected Business Functions
- Software Development CI/CD Pipelines (Jenkins, Jira, Confluence)
- Identity and Access Management / Single Sign-On (Keycloak, PingFederate)
- Artifact Repository and Software Supply Chain (JFrog Artifactory)
- Enterprise Application Servers and Java-based Web Services
Estimated downtime: 7 days
Estimated loss: N/A
The vulnerability enables unauthenticated remote code execution on servers running affected Java runtimes (Java 17.0.6+ on x86-64 AVX-512 VBMI-capable hardware), specifically Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate under default configurations. Successful exploitation could expose authentication credentials and session tokens processed by identity providers (Keycloak, PingFederate), software build secrets and pipeline environment variables (Jenkins), source code repository access tokens and project management data (Jira, Confluence), private artifact packages and signing keys (JFrog Artifactory), and any secrets stored in JVM memory accessible via the JavaBleed memory-read primitive. At scale, this could affect millions of enterprise deployments worldwide that have not yet patched. Data categories at risk include OAuth tokens, SAML assertions, CSRF tokens, TLS private keys, database credentials, and sensitive application configuration. No confirmed financial losses or confirmed in-the-wild exploitation were reported at time of synthesis; financial impact is expected to be significant once exploitation is weaponized given the breadth of affected enterprise tooling.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Inline IPS (Suricata) signatures for CVE-2026-114938 exploit patterns — including malformed Base64 strings ending in '=' with non-multiple-of-4 lengths in Authorization headers — to detect and block pre-authentication exploit attempts at the network perimeter before they reach vulnerable Java runtimes.
- • Enforce Zero Trust Segmentation with identity-based microsegmentation policies to isolate Jira, Jenkins, Keycloak, Confluence, Artifactory, and PingFederate workloads into least-privilege namespaces, ensuring a successful JVM compromise cannot be used to pivot laterally to adjacent services or access secrets beyond the compromised application's defined trust boundary.
- • Activate East-West Traffic Security monitoring on all workload-to-workload and service-to-service flows within cloud environments hosting Java-based applications, baselining normal inter-service communication patterns to surface anomalous lateral movement originating from a compromised application process.
- • Implement Egress Security & Policy Enforcement with FQDN-based filtering and strict outbound allow-lists on all application-tier workloads to block unauthorized reverse shell callbacks and data exfiltration channels established by a post-exploitation implant running within a compromised JVM process.
- • Enable Multicloud Visibility & Control to maintain centralized observability over traffic anomalies such as burst patterns of malformed requests, unexpected outbound connections from application hosts, and repeated JVM restart events, feeding these signals into automated incident response workflows to accelerate detection and containment of active exploitation attempts.



