A newly disclosed Java vulnerability has prompted urgent warnings from cybersecurity agencies in the United States, Europe and Asia. The flaw, tracked as CVE-2026-114938 and widely called Java4Shell, affects some Java runtimes and could allow an attacker to execute code remotely under specific conditions.
Oracle and the OpenJDK project published fixes on November 17, 2026. The following day, authorities urged organizations to check servers and third-party applications rather than assume their installations were unaffected.
Which Java versions are vulnerable, how serious is Java4Shell, and what should administrators update first?
What is Java4Shell, CVE-2026-114938?
Java4Shell is a memory-corruption vulnerability in the Base64 decoding implementation used by certain Java virtual machines.
A specially formed input may cause an affected JVM to crash. Under certain conditions, the vulnerability may enable remote code execution (RCE) without authentication.
The US Cybersecurity and Infrastructure Security Agency (CISA) issued an urgent advisory on November 17. The European Union’s cybersecurity response team (CERT-EU) published its own warning on November 18.
Oracle lists the vulnerability in its November 2026 security update with a CVSS 3.1 severity score of 8.1, categorized as high. Some independent assessments use different scores, so a reference to 9.2 in another report should not be confused with Oracle’s published 8.1 rating.
Which Java versions are affected?
CERT-EU identifies vulnerable builds across several supported Java families. The fixed Oracle/OpenJDK releases highlighted in its November 18 advisory are:
| Java version family | Fixed version |
|---|---|
| Java 17 | 17.0.21.1 |
| Java 21 | 21.0.13.1 |
| Java 25 | 25.0.5.1 |
| Java 27 | 27.0.1.1 |
| Oracle Java 8 performance builds | 8u513 |
The risk also affects certain GraalVM builds. Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine and Red Hat OpenJDK distributions require vendor-specific review.
The exact fixed version can differ among vendors, and some builds may take longer to be released. Checking a major version alone is therefore insufficient: the full runtime build and its vendor matter.
Is every Java application vulnerable?
No. Exploitation requires a combination of runtime, processor and data-handling conditions.
CERT-EU describes affected systems as running on x86-64 processors with the relevant AVX-512 capabilities, including the AVX-512 VBMI instruction set.
The application must also handle attacker-controlled Base64 data through a reachable code path. Examples of contexts where externally supplied encoded data may be processed include authentication-related headers and tokens.
ARM64 systems are not affected by this particular vulnerability, according to CERT-EU’s technical assessment.
Those restrictions are useful for prioritization. Nevertheless, organizations should not rely on a quick assumption that their applications never decode untrusted data. Checking runtime versions and vendor advisories is more reliable.
What should administrators do immediately?
CISA recommends identifying affected Java installations and applying the relevant vendor patches as quickly as possible, prioritizing internet-facing systems.
A practical defensive review includes:
- Inventory Java runtimes, including versions inside Docker images, appliances and vendor-supplied software.
- Check complete version/build numbers against the vendor’s November 2026 advisory.
- Patch supported vulnerable runtimes and restart the affected Java processes.
- Contact application vendors when their products bundle Java and cannot safely be updated independently.
- Monitor unexpected JVM crashes and other signs of suspicious activity.
To check the Java version used by a shell session, an administrator can run:
java -version
That command identifies the Java installation selected in the current environment; an application or service may be using a different bundled runtime.
What if a patch cannot be applied immediately?
CERT-EU describes temporary compensating controls for affected servers.
One option is to disable the relevant Base64 intrinsic with a JVM startup setting:
-XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics
The advisory also discusses limiting AVX support through another runtime option, while warning that doing so can affect performance.
These changes require restarting the JVM and should be validated against the application and Java vendor. They are interim measures, not substitutes for applying supported fixes.
Restricting access to internet-facing services and validating external input can also reduce exposure while an approved update is being deployed.
Has Java4Shell been exploited in real attacks?
Public security advisories available on November 18 did not establish a confirmed widespread exploitation campaign.
Some security researchers reported technical proof-of-concept work, which shows why the issue is taken seriously, but such claims are different from independently verified reports of active compromise.
CISA’s recommendation to patch applies regardless of whether known attacks have already occurred.
The flaw has also triggered official concern outside the US. Reuters reported cybersecurity warnings and precautionary action in South Korea, highlighting Java’s extensive use in public-sector and enterprise systems.
Does the vulnerability affect applications such as Jenkins or Keycloak?
Java-based applications and infrastructure services may be exposed if they use a vulnerable runtime on applicable hardware and process relevant input.
CERT-EU mentions products such as Keycloak, certain Atlassian applications and JFrog Artifactory as examples of software that uses affected Java platforms.
That does not mean every deployed instance of those products has been independently confirmed exploitable. Each case depends on its installed runtime, vendor fixes and deployment configuration.
The same principle applies to Java services deployed in Kubernetes or container environments: a patched host operating system does not automatically replace a vulnerable JVM inside an application image.
What matters most about the November Java update?
Java4Shell is a high-severity vulnerability for which patches are already available. The relevant flaw is CVE-2026-114938, and CERT-EU identifies Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 as fixed releases for the corresponding version families.
The decisive next step for operators is to identify their actual runtime builds, apply vendor-provided updates and restart affected JVMs. The risk is conditional, but the global warnings reflect the potential consequences for exposed Java applications.
Technical status and version information reflect Oracle, CISA and CERT-EU notices published November 17–18, 2026.