On this page · 7 sections
  1. Base64 Input Can Crash the JVM and Enable Code Execution
  2. Services That Accept Network Input Are the Exposed Systems
  3. Affected Oracle Java SE and GraalVM Versions
  4. Other Java SE Fixes in the Same Oracle Update
  5. Compensating Controls and Steps When Patching Is Not Feasible
  6. Checking Whether Oracle Java SE and GraalVM Installs Are Affected
  7. Sources

Security release

Status as of 2026-11-18

10 CVEs

Corporation Oracle Java SE

Highest CVSS8.1High
Exploited
None known · CISA SSVC
Published
2026-11-17

Most severe first

  1. CVE-2026-114938High8.1Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE
  2. CVE-2026-114939High7.4Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE
  3. CVE-2026-114940High7.4Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE
  4. CVE-2026-114941High7.0Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK product of Oracle Java SE (component: Compiler)
  5. CVE-2026-114942High7.0Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK product of Oracle Java SE (component: Libraries)
Show all 10
  1. CVE-2026-114943Medium6.5Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE
  2. CVE-2026-114944Medium5.9Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE
  3. CVE-2026-114945Medium5.3Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK product of Oracle Java SE (component: Libraries)
  4. CVE-2026-114946Medium4.8Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE
  5. CVE-2026-114947Low3.7Vulnerability in Oracle Java SE (component: JSSE)

Earlier CVEs this article mentions: CVE-2026-86144, CVE-2026-86137, CVE-2026-86138, CVE-2026-86139, CVE-2026-86140, CVE-2026-86141, CVE-2026-86142, CVE-2026-86143

Data: CVE records on cve.org

Check your project

Warning

Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition are affected by CVE-2026-114938, a memory-corruption flaw in the Base64 decoder of the x86-64 HotSpot JVM. CISA calls it a critical vulnerability. The CVE record assigns it a CVSS 3.1 base score of 8.1 (HIGH), assigned by Oracle.

Base64 Input Can Crash the JVM and Enable Code Execution #

CISA states that specially crafted Base64 input could crash the JVM and allow for unauthenticated remote code execution, and it urges organizations to patch immediately (CISA). The flaw is named Java4Shell, and it sits in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine, which is part of the Java Development Kit. Oracle credits Albert Yang and Quang Luong of Calif.io with reporting it (Oracle advisory), and CISA credits the Canadian Centre for Cyber Security (Cyber Centre) with contributing to the alert.

The CVE record describes the same flaw in different terms. It calls the vulnerability difficult to exploit, and it says an unauthenticated attacker with network access via multiple protocols can compromise the products, with takeover as the successful outcome (CVE record). The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. CISA's SSVC assessment on 2026-11-17 rates exploitation as none, so the exploitation rating and CISA's urgent patching call are both stated by their sources and should be read together.

Note

Background: The CVE record states that the vulnerability can only be exploited by supplying data to APIs in the specified component, without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. The record lists the component as Compiler, while CISA places the flaw in the Base64 decoder.

Services That Accept Network Input Are the Exposed Systems #

CISA asks operators to prioritize internet-facing systems when applying patches (CISA). Because the CVE record ties exploitation to data sent to APIs, such as through a web service, any service that decodes Base64 from network clients is the place to start. The exposure is not limited to standalone installs: CISA points to JDKs and Java runtimes bundled with third-party applications, included in container images, and shipped in appliances.

Inventory is the hard part. CISA warns that JDKs and Java runtimes may not appear as separate entries in software inventories. A search by product name alone can miss a runtime that a vendor packaged inside its application, so the inventory review has to cover those bundles too.

Affected Oracle Java SE and GraalVM Versions #

ProductSupported versions affectedFixed version
Oracle Java SE8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3Not printed in Oracle's advisory
Oracle GraalVM for JDK17.0.21.0.3, 21.0.13.0.3Not printed in Oracle's advisory
Oracle GraalVM Enterprise Edition21.3.20.0.3Not printed in Oracle's advisory

The same versions appear in the CVE record and in the risk matrix of Oracle's Critical Security Patch Update Advisory for November 2026, first released 2026-11-17. Neither source prints a fixed version number, so get the patched build for each line through Oracle's patch channels. The same advisory carries 11 new security patches for Oracle Java SE, all of them remotely exploitable without authentication, and CVE-2026-114938 has the highest CVSS score among them.

Other Java SE Fixes in the Same Oracle Update #

Patching for Java4Shell also installs the other Java SE fixes of the November 2026 advisory. Oracle's notes split them by exposure: some are reachable only through data sent to a component's APIs, such as a web service; some only through sandboxed Java Web Start applications or applets that run untrusted code; and some through both.

CVEComponentCVSS 3.1Oracle Java SE versions affectedExposure (Oracle's note)
CVE-2026-86144 (its patch also addresses CVE-2026-86137, CVE-2026-86138, CVE-2026-86139, CVE-2026-86140, CVE-2026-86141, CVE-2026-86142 and CVE-2026-86143)JavaFX (libxml2)7.5Java SE 8u511b33; JavaFX 21.0.13, 25.0.5, 27.0.1Sandboxed clients running untrusted code
CVE-2026-114939JGSS7.48u511b33, 8u511b33-perf, 11.0.33.0.3, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3Sandboxed clients running untrusted code
CVE-2026-114940JSSE (TLS)7.48u511b33, 8u511b33-perf, 11.0.33.0.3, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3APIs and sandboxed clients
CVE-2026-114941Compiler7.021.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3Data sent to the component's APIs
CVE-2026-114942Libraries7.021.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3Data sent to the component's APIs
CVE-2026-114943Hotspot6.58u511b33-perf, 11.0.33.0.3, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3APIs and sandboxed clients
CVE-2026-114944Core Java Libraries5.98u511b33, 8u511b33-perf, 11.0.33.0.3, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3APIs and sandboxed clients
CVE-2026-114945Libraries5.321.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3APIs and sandboxed clients
CVE-2026-114946Compiler4.88u511b33, 8u511b33-perf, 11.0.33.0.3, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3APIs and sandboxed clients
CVE-2026-114947JSSE (TLS)3.725.0.5.0.3, 27.0.1.0.3Sandboxed clients running untrusted code

Compensating Controls and Steps When Patching Is Not Feasible #

CISA's first step is to identify affected Java installations, and its guidance on what to check is concrete (CISA). The steps below follow the order CISA gives.

  1. Review the software inventory for JDKs and Java runtimes, including those bundled with third-party applications or included in container images and appliances; they may not appear as separate inventory entries.
  2. Apply relevant Java and vendor patches as soon as they are available, starting with internet-facing systems.
  3. If immediate patching is not feasible, restrict and validate Base64 input at the application boundary.
  4. If immediate patching is not feasible, enforce input-size limits on that input and limit unauthenticated access.
  5. Review Oracle's security advisory for patching guidance and the affected products and versions.
  6. Monitor for rogue runtimes, unexpected JVM crashes and suspicious Java processes.

Checking Whether Oracle Java SE and GraalVM Installs Are Affected #

Compare each installed runtime's version string with the table above, but do not treat a version missing from it as safe. Oracle states that releases outside Premier Support or Extended Support are not tested for these vulnerabilities and that it is likely that earlier versions of affected releases are also affected, and it recommends upgrading to supported versions (Oracle advisory). Run the comparison against every JDK found in the inventory, including bundled runtimes and container images. Oracle also points to its Java Management Service, available to all users, as a way to find vulnerable Java versions.

The Sentinel’s Call

Operators running any listed Oracle Java SE or GraalVM version should start with internet-facing systems, as CISA directs. Where patching must wait, the input-boundary controls, input-size limits and limits on unauthenticated access are the stated stopgaps. Monitoring for unexpected JVM crashes and suspicious Java processes should run in the meantime.

Our judgement, drawn only from the facts and sources above.

Sources

  1. Oracle Critical Security Patch Update Advisory - November 2026: Oracle Java SE Risk Matrix oracle.com · Nov 17, 2026
  2. Critical Java Vulnerability Requires Immediate Patching | CISA cisa.gov · Nov 17, 2026
  3. CVE-2026-114938: Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE cve.org · Nov 17, 2026

More on CISA alerts

2 other articles, newest first

Next reading

Edited and approved by Jarosław Krzemiński. Spotted a mistake? Report a correction or read the corrections policy.