Security advisory · Runtimes and languages

CVE-2026-114938: the 'java4shell' flaw in the Java compiler

Updated November 18, 2026By HostCrust4 min read

CVE-2026-114938, nicknamed Java4Shell, is a high-severity flaw in the Java compiler shared by Oracle Java SE, Oracle GraalVM and OpenJDK. A remote, unauthenticated attacker can send crafted data to the compiler and take over the JVM. Patch to a fixed release from your Java vendor and restart the service; CISA has urged immediate patching.

CVE ID
CVE-2026-114938
Published
November 17, 2026
CVSS
8.1 (High), Oracle/NVD; 9.8 preliminary, Red Hat
Affected
Oracle Java SE & GraalVM; distribution OpenJDK 17+ builds
Fixed in
Oracle Nov 2026 release; OpenJDK updates rolling out, then restart the JVM
Assigned by
Oracle

What is CVE-2026-114938 (java4shell)?

CVE-2026-114938 is a vulnerability in the compiler component shared by Oracle Java SE, Oracle GraalVM and the open-source OpenJDK the rest of the Java ecosystem is built on. According to Oracle's advisory, an unauthenticated attacker with network access can supply crafted data to the affected compiler APIs — for example through a web service that compiles or processes input — and, on a successful attack, take over the Java runtime completely, with impact to confidentiality, integrity and availability. It does not rely on the old Java Web Start or browser-applet attack surface. Oracle rates it difficult to exploit; Red Hat's preliminary analysis of the same flaw in OpenJDK rates the attack complexity lower and describes it as a memory-corruption bug on x86-64 processors with the AVX-512 VBMI feature. CISA issued an alert on 17 November 2026 that names this CVE, urges immediate patching, and refers to the flaw as “Java4Shell.”

Am I affected?

You're affected if you run an affected Java distribution and expose any path that feeds attacker-controlled data to the compiler. The NVD record lists these affected versions: 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 Oracle GraalVM Enterprise Edition 21.3.20.0.3.

Because the flaw is in code shared with OpenJDK, distribution OpenJDK builds are affected too. Red Hat is investigating which of its OpenJDK builds are affected (java-17-openjdk and java-21-openjdk; security bulletin RHSB-2026-018); Debian and Ubuntu track it against openjdk-17, -21 and -25 (Debian's unstable build is fixed, with its stable update still to come; Ubuntu tracks it too); and Amazon Corretto shipped a fix in 27.0.1.1.4 on 17 November 2026. Red Hat's preliminary analysis notes the memory-corruption condition it studied affects OpenJDK 17.0.6 and later on x86-64 CPUs with AVX-512 VBMI, and says ARM64 is not known to be affected. Check what you run with java -version.

How do I fix it?

Patch to a fixed release from your Java vendor, then restart the JVM — a patched runtime on disk does nothing until the running process restarts.

  • Oracle Java SE / GraalVM: apply the Java SE patch in Oracle's November 2026 Critical Security Patch Update.
  • RHEL / AlmaLinux / Rocky Linux OpenJDK: install the java-17-openjdk / java-21-openjdk update once your distribution publishes it (RHSB-2026-018), then restart the service.
  • Debian / Ubuntu OpenJDK: apply the openjdk security update for your release when it lands, then restart.
  • Amazon Corretto: upgrade to 27.0.1.1.4, or the patched build for your Java line.

Until you can patch, CISA suggests compensating controls: validate and restrict Base64 input at the application boundary, enforce input-size limits, and limit unauthenticated access. Oracle rates exploitation as difficult, but CISA still urges immediate action, so prioritise internet-facing Java services first. Our guide to Linux vulnerability scanners covers finding affected packages across a fleet.

Oracle JDK vs OpenJDK — and what HostCrust tracks

It's worth being precise about what a patch-management tool can and can't do here, because this CVE spans two different worlds.

Oracle's proprietary JDK and GraalVM are not distributed through your Linux distribution's package manager and carry no distribution security data. HostCrust does not patch or track Oracle's JDK — if you run it, you apply Oracle's November 2026 release yourself.

Your distribution's OpenJDK — for example java-17-openjdk on RHEL, AlmaLinux and Rocky Linux, or openjdk-17-jre on Debian and Ubuntu — is an ordinary distribution package with its own security advisories. Patch Proof checks those packages against your distribution's security data, so once your distribution publishes its fix for CVE-2026-114938, Patch Proof will show that package as open until the update is installed. And because a running JVM keeps the old code loaded, the real fix isn't done until the service is restarted — the same running-versus-installed gap you get with kernel patches.

How we checked this: Every fact on this page — the CVE id, the affected and fixed versions, the CVSS scores and the remediation — was taken from the NVD record and the vendor and distribution advisories (Oracle, CISA, Red Hat, Debian, Ubuntu and Amazon Corretto) linked under Sources, and checked on November 18, 2026. HostCrust did not independently reproduce the vulnerability, and this is a fast-moving advisory: confirm the current fixed version with your vendor. Anything we didn't run ourselves comes from the official documentation listed under Sources.

Check which CVEs are really open on your server

HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.

Run the free check About Patch Proof

FAQ

Is this the same as Log4Shell?

No. Log4Shell (CVE-2021-44228) was in the Log4j logging library; CVE-2026-114938 is in the Java compiler itself and is shared across Oracle Java SE, GraalVM and OpenJDK. The “java4shell” nickname reflects how seriously the industry is treating it, not a shared root cause. Treat it on its own facts: patch the JVM and restart.

Does CVE-2026-114938 affect OpenJDK or only Oracle Java?

Both. Oracle assigned the CVE for its Java SE and GraalVM products, but the flaw is in code shared with OpenJDK, so distribution OpenJDK builds are affected as well. Red Hat is investigating which of its OpenJDK builds are affected, Debian and Ubuntu track it against openjdk-17, -21 and -25, and Amazon Corretto shipped a fix in 27.0.1.1.4.

What's the real severity — 8.1 or 9.8?

It depends on who scored it. Oracle and the NVD record list CVSS 3.1 base 8.1 (High), rating the attack complexity as high. Red Hat's preliminary analysis of the same flaw in OpenJDK scores the CVSS base at 9.8 with lower attack complexity. Scores from different sources often differ early in a CVE's life; either way, patch promptly, starting with internet-facing services.

Do I need to restart after patching?

Yes. A running Java process keeps the old code loaded in memory, so updating the JAR or runtime on disk changes nothing until you restart the JVM or its service. After installing the fix, restart the affected application and confirm it came back up on the patched runtime.

Sources

  1. NVD: CVE-2026-114938
  2. Oracle Critical Security Patch Update Advisory, November 2026 (lists CVE-2026-114938 and the Java SE patch)
  3. CISA alert: Critical Java Vulnerability Requires Immediate Patching (Nov 17, 2026)
  4. Red Hat: CVE-2026-114938 (OpenJDK, security bulletin RHSB-2026-018)
  5. Debian security tracker: CVE-2026-114938 (openjdk-17 / -21 / -25 / -27)
  6. Ubuntu security: CVE-2026-114938 (openjdk-8 / -17 / -21 / -25, fixes pending)
  7. Amazon Corretto 27 changelog: 27.0.1.1.4 addresses CVE-2026-114938