← Back to blog

Critical Java4Shell Flaw Enables Pre-Auth RCE in Popular Enterprise Apps

A new Java vulnerability, CVE-2026-114938, allows unauthenticated remote code execution in Jira, Jenkins, Keycloak, and more. Oracle plans to patch 11 Java flaws, including this critical RCE.

TL;DR

  • CVE-2026-114938 (Java4Shell) enables pre-auth RCE in major apps like Jira and Jenkins.
  • Impacts Java 17.0.6+ on x86-64 CPUs with AVX-512 VBMI support.
  • Oracle will release fixes for 11 Java vulnerabilities on Nov 17, 2026.
  • Maximum CVSS score is 8.1; all flaws exploitable remotely without auth.
  • Organizations should prepare to prioritize patching after Oracle’s update.

A newly disclosed Java vulnerability known as Java4Shell (CVE-2026-114938) poses a significant risk to organizations using popular enterprise applications such as Jira, Jenkins, and Keycloak. The flaw enables attackers to execute arbitrary code without authentication, making it especially dangerous.

Security researchers from Calif have confirmed that the issue affects Java 17.0.6 and newer versions, but only when running on x86-64 processors that support the AVX-512 VBMI instruction set. Oracle has announced plans to address this and ten other remotely exploitable Java vulnerabilities in its upcoming patch update scheduled for November 17, 2026.

Vulnerability Overview

  • CVE-2026-114938, dubbed Java4Shell, allows unauthenticated remote code execution.
  • Affects widely-used platforms including Atlassian Jira, Jenkins, Red Hat Keycloak, and others.
  • Limited to systems running Java 17.0.6+ on specific x86-64 architectures with AVX-512 VBMI support.
  • No user credentials required for exploitation, increasing attack surface significantly.

Vendor Response and Mitigation

  • Oracle’s next Critical Patch Update (CPU) on November 17, 2026 will include fixes for 11 Java SE vulnerabilities.
  • All 11 flaws can be exploited remotely without authentication; highest CVSS severity is 8.1.
  • Enterprises should monitor Oracle’s advisory closely and plan for immediate deployment post-release.
  • Until patched, consider restricting access to affected applications and monitoring logs for suspicious activity.

Sources

Sources

Security email updates

One digest email when we publish new security articles (TL;DR plus links to read more). Unsubscribe anytime from the message footer. See our Privacy Policy.