CVE-2026-114938
November 18, 2026
·
0
Minutes Read

655 Patch Oracle CSPU, Java4Shell

Advisory
Security Advisory
November 18, 2026
·
0
Minutes Read

655 Patch Oracle CSPU, Java4Shell

Advisory
Security Advisory
November 18, 2026
·
0
Minutes Read
Kudelski Security Team
Find out more
table of contents
Share on
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Update: 2026-11-18

  • Calif disclosed CVE-2026-114938 (Java4Shell) on 17 Nov 2026. The root cause is reported as a flaw in OpenJDK's AVX-512 Base64 intrinsic.
  • Oracle's CSPU patched builds shipped at 21:00 UTC on 17 Nov: JDK 17.0.21.1 (GA), JDK 21.0.13.1 (GA), 25.0.5.1 (GA), 27.0.1.1 (GA).
  • Denial of service is more readily achievable than RCE. There is no "skeleton key" exploit affecting all Java applications.
  • Exploitation is limited to x86-64 CPUs with AVX-512 VBMI support. ARM64 is not affected.
  • Calif reports interim JVM flags (-XX:-UseBASE64Intrinsics, -XX:UseAVX=2). These are temporary mitigations; they are not a patch.

Summary

Oracle released a Critical Security Patch Update (CSPU) on 17 November 2026 with 655 new security patches across its portfolio, including 11 patches for Oracle Java SE. Oracle states all 11 Java SE vulnerabilities may be remotely exploitable over a network without requiring authentication; the highest Java SE CVSS v3.1 base score is 8.1.

The same day, Calif disclosed Java4Shell: an unauthenticated RCE caused by memory corruption in OpenJDK's Base64 decoder tracked as CVE-2026-114938, rated CVSS 4.0 9.2 (Critical), affecting OpenJDK 17.0.6 and later. OpenJDK also published an advisory that day, and Oracle's CSPU patched builds (which cover Java4Shell) shipped at 21:00 UTC.

Affected Systems and/or Applications

Java SE and related runtimes: Oracle lists Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, plus Oracle GraalVM Enterprise Edition 21.3.20.0.3, Oracle GraalVM for JDK 17.0.21 and 21.0.13, and Oracle JavaFX 21.0.13, 25.0.5 and 27.0.1.

Affected by Java4Shell/CVE-2026-114938: Java 17 from 17.0.6 up to 17.0.21.1, Java 21 before 21.0.13.1, Java 25 before 25.0.5.1, and Java 27 before 27.0.1.1. The Java 17 range covers roughly four years of builds, from January 2023. Because OpenJDK is redistributed by many vendors, fixes may arrive on different dates under different version names. Exploitation requires x86-64 CPUs with AVX-512 VBMI support. ARM64 is not affected. Exposure requires attacker-controlled data to reach the basic or URL Base64 decoder (Base64.getDecoder(), Base64.getUrlDecoder()); the MIME decoder is not affected.

Java 17 remains a long-term support release widely used by banks, cloud providers and back-end systems, so exposure is likely to be broad. Inventory should cover the exact JVM, vendor and build in use, including Java inside containers, appliances and third-party applications.

The same CSPU also covers Oracle Database Server, APEX, REST Data Services, Communications, E-Business Suite, Fusion Middleware, Analytics, Hyperion, MySQL, PeopleSoft, Siebel, Supply Chain and VirtualBox, among others.

Consult the Oracle CSPU advisory for the complete product, component and version matrix.

Technical Details

Oracle’s "remotely exploitable without authentication" classification means the attack path can occur over a network and need not require valid credentials. It does not mean every Java installation is exploitable; applicability depends on the affected component being present and enabled, the vulnerable functionality being reachable over a network, configuration, and prerequisites that will appear in the final risk matrix.

Java4Shell's root cause is reported. Handwritten AVX-512 assembly in OpenJDK's Base64 intrinsic mishandles = padding in positions valid Base64 never uses. That produces a negative output length, which becomes a 64-byte write past the buffer. Java rejects the input only after the overwrite, so application-side input validation doesn't help.

Attack surface. Calif demonstrated pre-auth RCE against default configs of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and post-auth RCE against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Datadog states that reliable RCE needs work tailored to each application and JVM, and that no single universal exploit exists.

Patches are shipped. Oracle's CSPU includes patched builds. Oracle's JDK 17 release-notes index lists JDK 17.0.21.1 (GA) as its newest entry, and the JDK 21 notes list 21.0.13.1 (GA). Also fixed are 25.0.5.1 (GA), 27.0.1.1 (GA).

Oracle's published CSPU advisory states that the CSPU contains 655 new security patches and that Oracle "strongly recommends that customers remain on actively-supported versions and apply security patches without delay."

Mitigation

  • Inventory Java runtimes now. Record the executable path, vendor, full version and build for every JVM, including those inside containers, appliances and third-party products.
  • Apply the CSPU fixes promptly, prioritising exposed and business-critical systems, and restart affected Java processes so running instances load the corrected components.
  • Use vendor-supplied fixes. Obtain patches through My Oracle Support or from appliance, hosting and OpenJDK vendors, and confirm the correct fixed build rather than swapping in a standalone JDK.
  • Reduce unnecessary external exposure as an interim measure. Close internet access the business does not need and keep backups ready for rollback.
  • Interim JVM options (not a patch). Calif reports -XX:-UseBASE64Intrinsics (disables the accelerated Base64 path) and -XX:UseAVX=2 (disables AVX-512, x86-64 only). Both need a restart and may reduce performance. Datadog tested both. -XX:UseAVX=2 fails to start on ARM64 JVMs, so pass it only on x86-64 hosts.
  • Check exposure. On x86-64 hosts, grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo shows VBMI support. Run jcmd <PID> VM.version against the bundled runtime to confirm its version, and jcmd <PID> VM.flags -all to check effective flags.

What the CFC is Doing

The CFC is monitoring the situation and analyzing the case to identify potential threat-hunting campaigns. This advisory will be updated if required.

References

‍

Related Post