THREAT LEVEL - HIGH

18-11-2026

High Level – New Critical Java Vulnerability (Java4Shell) Could Allow Remote Code Execution

Threat Level Description

IthacaLabs has maintained the Threat Level (High) adding a new observation:

An attack is highly likely. Addressing the broad nature of the threat in order to reach an acceptable risk level, requires additional and sustainable protective security measures combined with specific business and geographical vulnerabilities and judgments.

Description

We have observed a new critical vulnerability in Java, known as Java4Shell, that can allow remote, unauthenticated attackers to execute code on systems running affected Java versions.

The critical vulnerability, CVE-2026-114938, is a memory-corruption flaw in the Base64 decoder of the HotSpot Java Virtual Machine. Specially crafted input can crash the application or allow remote code execution. It affects Java running on x86-64 processors that support the AVX-512 VBMI instruction set. ARM64 systems are not known to be affected.

Researchers have demonstrated remote code execution without authentication in widely used Java applications, including Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, in their default configurations. They have published a proof-of-concept trigger but are withholding the product-specific exploits, and the flaw is not currently listed by CISA as known to be exploited.

Researchers also report that Java programs opening a TLS connection to a malicious server can be compromised. Oracle and OpenJDK have released fixes, while Red Hat and Ubuntu updates are still pending, and CISA urges organizations to patch immediately. Organizations running Java, including Java bundled inside third-party products, container images and appliances, may be at elevated risk of compromise.

Our Advisory and Managed Services, including our Security Operations and Technology Resilience lines, can help safeguard your organization against such threats.

Through proactive monitoring, threat detection, and incident response, our services are designed to keep your systems secure, resilient, and prepared for evolving cyber risks. We advise all organizations to remain vigilant and regularly review their cybersecurity postures.

Affected Products:

  • OpenJDK 17 from 17.0.6, up to and including 17.0.21.0.3
  • OpenJDK 21, 25 and 27, up to and including 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3
  • Oracle Java SE 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 GraalVM Enterprise Edition 21.3.20.0.3
  • Red Hat build of OpenJDK 17, 21 and 25, and Red Hat Enterprise Linux 8, 9 and 10
  • Red Hat products bundling Java, including Red Hat build of Keycloak and JBoss EAP 7 and 8
  • Ubuntu 18.04, 20.04, 22.04, 24.04 and 26.04 LTS, and Ubuntu 26.10

Recommendation(s):

It is highly recommended to apply the Java security updates from Oracle, OpenJDK and your Java distribution vendor as soon as they are available, and to update applications that bundle their own Java runtime as their vendors release fixes. Organizations should also consider the following measures:

  • Identify all Java installations, including runtimes bundled with third-party applications, container images and appliances.
  • Prioritize internet-facing systems running Java on x86-64 processors with AVX-512 VBMI, which Red Hat and the researchers report exploitation depends on.
  • Where patching must wait, start Java with the -XX:-UseBASE64Intrinsics option, which disables the vulnerable hardware-accelerated Base64 decoder.
  • If immediate patching is not feasible, apply temporary controls such as validating Base64 input, enforcing input-size limits and limiting unauthenticated access. These do not replace the fixes.
  • Monitor for unexpected Java crashes, rogue Java runtimes and suspicious Java processes.
  • Ensure incident response teams are prepared to investigate and rebuild any system suspected of compromise.

You should understand the importance of applying security updates with urgency, regardless of organizational size. Implementing an effective patch management strategy, enabling comprehensive event logging, and actively monitoring security events are critical to protecting business-critical assets. A comprehensive risk management approach should include regular penetration testing, at least annually and after significant system changes, to ensure continued compliance with security best practices and industry regulations.

Threat Level Description:

Threat Level: High – An attack is highly likely. Addressing the broad nature of the threat in order to reach an acceptable risk level, requires additional and sustainable protective security measures combined with specific business and geographical vulnerabilities and judgments.

References:

Critical Java Vulnerability Requires Immediate Patching (CISA)

Oracle Critical Security Patch Update Advisory – November 2026

OpenJDK Vulnerability Advisory: 2026/11/17

CVE-2026-114938 – CVE Record

CVE-2026-114938 – NIST National Vulnerability Database

IthacaLabs Incident Response and Threat Intelligence Services

SIGN UP

Get the latest Threat Alerts in your inbox.