Monocera · ISO 27001 · C.A.R.L.
Security Advisory · CVE-2026-114938
18 November 2026
Critical vulnerability · OpenJDK

Java4Shell: Critical flaw in OpenJDK.

Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in OpenJDK, the most widely used Java runtime, disclosed on 17 November 2026. It is rated 9.2 (Critical) under CVSS 4.0 and could let an attacker crash or, in some cases, run code on a server that processes their input.

There are no reports of it being exploited in the wild. Monocera has inventoried Java across every managed client environment and is remediating the systems at risk, starting with anything reachable from the network.

Monocera managed clients do not need to take action. We will contact you directly if a system in your environment needs a change or a maintenance window.

What is affected

The flaw sits in Java's built-in Base64 decoder. It affects OpenJDK 17, 21, 25 and 27, per the OpenJDK advisory. Oracle's November 2026 Critical Security Patch Update also lists an affected Java 8 build.

Java versionsOpenJDK 17, 21, 25 and 27
DistributionsOracle Java SE and OpenJDK, Eclipse Temurin, Microsoft Build of OpenJDK, Amazon Corretto, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle GraalVM
ApplicationsAny application that ships or runs on an affected runtime, including Atlassian Jira and Confluence, Jenkins and Keycloak
HardwareOnly processors with AVX-512 VBMI: recent Intel Xeon (Ice Lake, Sapphire Rapids), AMD Zen 4 and Zen 5 (EPYC Genoa/Turin, Ryzen 7000/9000), and Intel 2019–2021 client chips

The hardware condition matters. Most Intel desktops and laptops from 12th generation onwards, and ARM-based systems, do not run the vulnerable code. Many cloud and on-premises servers do.

Many business applications bundle their own copy of Java. Standard Java or Windows updates do not patch these; the application vendor must release an update.

Current status

  • Exploitation: not known to be exploited in the wild as of 18 November 2026.
  • Impact: independent testing found that crashing an affected service is easy if an attacker can reach code that decodes their Base64 input. Running code is much harder and needs application-specific techniques.
  • Fixes: Oracle released fixed builds in its November 2026 Critical Security Patch Update. Temurin, Microsoft, Corretto, Zulu and other vendors are publishing their own fixed builds.
  • Temporary mitigation: where patching must wait, disabling the affected optimisation with the JVM option -XX:UseAVX=2 stops the overflow. Test before production use, as it can affect performance.

We expect researchers to publish proof-of-concept code in the coming days and will update this advisory as the picture changes.

What Monocera is doing

We started our response on 17 November, the day of disclosure, and are working through every managed environment in order of risk. Each affected client has a dedicated ticket tracking findings, actions and any accepted risk.

01
Inventory
Every managed Windows device has been scanned for Java, including copies bundled inside applications. For each one we record the version, whether it is running, whether it accepts network connections, and whether the host firewall allows them.
02
Prioritise
Internet-facing Java services come first, then services reachable from other internal systems, then desktop-only installs. Having Java installed is not the same as being at risk; what matters is whether an attacker can reach it.
03
Reduce exposure
Where a system is reachable, we restrict access with firewall rules or network controls straight away, before patching is complete.
04
Patch
We deploy fixed Java builds as each vendor releases them. For applications with bundled Java, we are working with the software vendors to get updates, and we schedule upgrades with you where downtime is needed.
05
Remove
Old or unused Java installs are removed, cutting the attack surface beyond this one flaw.
06
Monitor
Our 24/7 security operations partner is watching for signs of exploitation across managed endpoints. If exploitation is reported, we will step up threat hunting on affected systems.

What you should do

Monocera managed clients

No action needed. If your environment is affected, your Monocera team will contact you with the findings and any planned changes.

Please let us know about any Java-based software you run that we may not manage directly, such as vendor-hosted or line-of-business applications.

Other organisations
  • Find every Java runtime in your environment, including copies bundled with applications.
  • Check which are reachable from the internet or other systems, and restrict access where you can.
  • Apply your Java vendor's November 2026 fixed build, and ask application vendors for updated releases.
  • Remove Java where it is not needed.

References

Update log

18 Nov 2026Advisory published
Monocera® · Augmenting Business®November 2026