Summary
- CERT-EU has warned about CVE-2026-114938, a memory corruption vulnerability rated 8.1 under CVSS v3.1.
- Exploitation requires particular x86-64 processor features, an active accelerated decoding function and attacker-controlled Base64 input.
- Oracle and OpenJDK released fixes on 17 November; operators should prioritise exposed services and restart affected Java processes after patching.
European organisations are being urged to patch vulnerable Java systems after security researchers identified a memory corruption flaw that can crash applications and may, under specific circumstances, allow attackers to execute code remotely without authentication.
CERT-EU issued an advisory on 18 November concerning CVE-2026-114938, a high-severity vulnerability in OpenJDK and related Java distributions. Oracle and the OpenJDK project released fixes the previous day, while security researchers have published technical analysis explaining which systems are susceptible.
The flaw affects an optimised Base64 decoding function within the Java Virtual Machine. Exploitation requires a particular combination of processor capabilities and application behaviour, meaning Java installations do not face identical exposure simply because they use an affected software version.
CERT-EU has assigned the vulnerability a CVSS v3.1 score of 8.1 and recommends prioritising internet-facing applications. The issue has been informally described as Java4Shell, although it is unrelated to the Log4Shell vulnerability that affected Java logging software in 2021.
Hardware determines which code runs
The Java Virtual Machine can use specialised processor instructions to accelerate some computing operations. When supported hardware is available, OpenJDK may select an optimised execution path rather than a more general software implementation.
The vulnerable path processes Base64-encoded information, a common format for representing binary data as text. Applications may encounter such information when handling authentication credentials, web requests, tokens and other messages exchanged between systems.
Researchers at VulnCheck identified an error in the accelerated decoding implementation that can corrupt memory when it processes specially constructed input. The defect is associated with x86-64 processors supporting AVX-512 instruction features required by that implementation.
CERT-EU specifies AVX512F, AVX512BW, AVX512VBMI and BMI2 as the relevant capabilities. Its advisory identifies Intel Xeon Ice Lake or later and AMD Zen 4 or later among the processor families that can meet those conditions.
ARM64 systems are not affected by this particular vulnerability. Some older Intel processors and other x86-64 systems also lack the required instruction set, causing Java to use a different decoding implementation.
Hardware compatibility alone is insufficient for an attack. The accelerated function must be active, and an attacker must be able to supply Base64 data that reaches the vulnerable decoder through the application’s normal processing.
Potential entry points include authentication information or other encoded data handled by web services. Whether such a path exists depends on the application and the components processing external requests, rather than the Java version alone.
Service crashes are easier to reproduce
VulnCheck reproduced the memory corruption on affected Ice Lake hardware and demonstrated that suitable inputs could crash a vulnerable Java process when the relevant decoding function was reachable.
The researchers found that repeated requests could produce a denial-of-service condition in their test environment. Individual requests did not necessarily crash the application, because memory allocation behaviour could absorb some of the corruption without an immediate visible failure.
Remote code execution presents a more demanding challenge. According to VulnCheck, an attacker would need additional techniques to manipulate memory and obtain information required to bypass address randomisation protections.
The distinction affects the assessment of immediate risk. A service vulnerable to crashes may be susceptible to interruption, while reliable execution of attacker-controlled code would require further conditions and exploitation work.
VulnCheck’s public analysis describes a proof of concept for triggering the vulnerability but does not establish a generally reproducible remote code execution exploit. The company also reported no known exploitation in the wild at the time of its assessment.
Absence of known exploitation is not proof that attackers cannot develop new methods. Nevertheless, describing the flaw as universally exploitable would overstate the evidence and disregard the technical conditions identified by researchers.
Organisations should therefore combine the published severity rating with an assessment of their hardware, Java distributions and exposed applications when deciding which systems require the most urgent attention.
Several Java versions require updates
CERT-EU lists vulnerable versions across Java 17, 21, 25 and 27, alongside particular Java 8 performance builds and affected GraalVM releases. Corrected versions include 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
Java 8 performance builds have a separate version requirement, with Oracle identifying 8u513 as the corrected release for the affected build. Administrators should consult the advisory relevant to their exact distribution rather than assuming that a patch number from one branch applies to another.
The issue also concerns distributions based on OpenJDK. CERT-EU identifies Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft’s OpenJDK build, BellSoft Liberica, SAP SapMachine and Red Hat’s distribution among products requiring attention.
Those vendors maintain their own update schedules. A supplier may therefore provide a corrected build under a different version identifier or incorporate the fix into an application that bundles its own Java runtime.
Enterprise products using Java include identity management, development and application infrastructure. CERT-EU names Keycloak, certain Atlassian products and JFrog Artifactory as examples of software supported by affected Java technologies.
The use of Java by such a product does not establish that a particular installation is exploitable. Customers must still check the bundled runtime, deployment architecture and whether application inputs can activate the vulnerable decoding path.
Process restarts are part of remediation
CERT-EU recommends installing the relevant vendor fixes and restarting affected Java processes afterwards. Updating software files without restarting a running Java Virtual Machine may leave the old code active in memory.
Where immediate patching is impossible, the advisory identifies temporary configuration changes that can disable the vulnerable accelerated decoding function or prevent Java from using AVX-512 instructions.
Those options also require a restart and may affect performance. Administrators should test them against the relevant application, particularly where the service supports authentication, financial transactions or other essential business operations.
Software inventories become important because a business may operate Java through applications maintained by several suppliers. Some runtimes are installed directly by internal engineering teams, while others are embedded in commercial software or stored in container images used by automated deployments.
Identifying the affected versions is therefore only one part of remediation. Application owners also need to establish which systems use susceptible processors, whether external inputs reach the relevant decoder and how a patch can be introduced without unnecessary disruption.
The CERT-EU advisory provides a basis for prioritising that work. Internet-facing applications meeting the vulnerability’s technical conditions warrant prompt attention, while other installations can be assessed through the same evidence rather than treated as equally exposed.












