CVE-2026-114938: Choose the November Java patch for your runtime
Update affected Java runtimes for CVE-2026-114938 using the fixed build for their vendor and release branch. Azul shipped its November security update on November 17, 2026. Include embedded runtimes and container images in the rollout; updating a workstation’s default Java installation does not update a service’s bundled runtime.
Keep the severity ratings attributed
Azul’s advisory treats this vulnerability as Critical and cites CVSS 4.0 at 9.2. It describes OpenJDK’s CVSS 3.1 rating as 8.1, High. Oracle’s November advisory also assigns 8.1 under CVSS 3.1. Keep the scoring version and source with each number in patch records; do not relabel Oracle’s score as Critical or substitute one score for the other.
Select the matching Azul build
The Azul Zulu November release notes identify these fixed builds for the affected Java branches:
| Java | Update line | Zulu build | JDK build |
|---|---|---|---|
| 27 | CSPU for PSU | 27.30.201 CA / 27.30.202 SA | 27.0.1.1+4 |
| 25 | CSPU for PSU | 25.38.201 CA / 25.38.202 SA | 25.0.5.1+2 |
| 25 | CSPU for CPU | 25.37.202 SA | 25.0.4.1.201+1 |
| 21 | CSPU for PSU | 21.54.201 CA / 21.54.202 SA | 21.0.13.1+2 |
| 21 | CSPU for CPU | 21.53.202 SA | 21.0.12.1.201+1 |
| 17 | CSPU for PSU | 17.70.201 CA / 17.70.202 SA | 17.0.21.1+2 |
| 17 | CSPU for CPU | 17.69.204 SA | 17.0.20.1.201+1 |
CA means Community Availability; SA means Subscriber Availability. CSPU for CPU and CSPU for PSU are separate update lines. Match the installed line and subscription entitlement when choosing a package. A lower-looking CPU version can contain the fix; a single numeric threshold across lines is unreliable.
For Azul Prime, the November CVE fixes page lists stable 26.08.110.0 for the 26.08 line and 26.02.510.0 for the 26.02 line. It lists no Stream-line build in that table. Azul’s product support advisory confirms that each fixed Prime build covers the Java versions supported by its line.
Zulu 8 and 11 are not affected by this CVE according to that support advisory, while Prime’s affected Java versions include 8 and 11. Do not transfer one product’s exemption to the other. Unsupported Prime lines need a move to a supported fixed line.
Use product-specific guidance for other distributions
Oracle’s CVE row lists affected Oracle Java SE builds including 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. Those are affected builds, not upgrade targets. Use the advisory’s Java SE patch-availability guidance for the installed Oracle product; GraalVM has separate product entries.
For another distributor or an application with bundled Java, obtain its fixed package or image for this CVE. Record the complete vendor build and package revision. A Java major version alone cannot establish patch status, and the Azul table is not a mapping for other vendors.
Confirm installation and running-service versions
Inventory the runtime path selected by each service, its vendor and full version, and the package revision or container image digest. Check service launch configuration and deployment manifests as well as interactive shell defaults. Record every replica and standby instance.
Inspect version information from the actual installed runtime selected for the service through normal administrative access. Compare its full build identifier with the applicable vendor release. This checks the installed executable; it does not prove that an already running JVM has been replaced.
Deploy through the supported package or image channel, then restart or roll the application instances using the normal maintenance procedure. Verify the runtime identity reported by each newly started service and confirm that old instances have stopped. For containers, confirm the deployed digest rather than relying on a mutable tag.
Check ordinary application health and representative workloads before extending the rollout. Retain a recovery plan that does not silently restore an affected runtime. Record the fixed build, completed restarts and any outstanding instances in the change record. These are deployment checks, not tests of exploitability.
Acknowledgements
This post was created with assistance from AI.