Oracle and the OpenJDK project released fixes November 17 for CVE-2026-114938, a memory-corruption vulnerability sometimes called Java4Shell. Oracle assigns the flaw a CVSS score of 8.1 and says it can be reached remotely without authentication when data is supplied to the affected compiler component through an application such as a web service.
CERT-EU says successful exploitation can crash an affected service and, in some circumstances, allow unauthenticated remote code execution. That does not mean every application written in Java is vulnerable. Exposure depends on the Java release, processor features, runtime configuration and whether attacker-controlled Base64 data reaches the affected decoder.
The reviewed advisories establish a software vulnerability and available fixes. They do not establish that a dealership, automotive vendor or customer system has been compromised through it.
Beyond automotive: what is confirmed
CERT-EU says the vulnerable path requires all of the following: an x86-64 processor with specified AVX-512 and BMI2 capabilities, an active Base64 intrinsic, and attacker-controlled Base64 data reaching the decoder. It says ARM64 systems are not affected. Red Hat similarly says x86-64 systems without the required AVX-512 capability are not currently known to be affected.
The risk is broader than a single vendor because Java runtimes can be embedded in applications and infrastructure. CERT-EU identifies Oracle Java SE and OpenJDK release lines, GraalVM releases and multiple OpenJDK-based distributions as affected, while noting that each distributor publishes fixes on its own schedule. A product that bundles its own Java runtime needs a product-vendor update or confirmation; replacing a separate workstation Java installation may not update that bundled runtime.
Affected and fixed release lines
CERT-EU lists Oracle Java SE 8 performance build 8u511-perf, OpenJDK 17 from 17.0.6 through 17.0.21, Java 21 through 21.0.13, Java 25 through 25.0.5 and Java 27 through 27.0.1 among the affected releases. It identifies fixed Oracle or OpenJDK releases as 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. GraalVM and other OpenJDK distributions require vendor-specific confirmation.
Red Hat's November 17 page says its build-specific analysis was still in progress and labels its own scoring preliminary. That is a reason to follow the supplier's current advisory for the actual installed package, not to translate one version table across every distribution.
Why it matters
Dealerships depend on third-party systems for customer records, vehicle inventory, credit workflows, service scheduling, parts and identity. DTR has not established which of those products use an affected Java runtime. The transferable control is to make vendors resolve the dependency question to an exact product, runtime and hosting environment.
An availability message is not a patch record. A provider should be able to state whether the affected code is present and reachable, which fixed package or mitigation was applied, whether every Java virtual machine was restarted and what evidence supports the answer.
What dealerships and technology providers should do
Prioritize internet-facing applications and ask each responsible provider whether it runs an affected Oracle, OpenJDK, GraalVM or bundled runtime on a processor that meets the vulnerable conditions. Record the installed and fixed versions, the vendor advisory used, the change time and the restart result. Do not assume a cloud-hosted product is unaffected, and do not assume it is vulnerable without confirmation.
CERT-EU recommends updating and restarting all affected Java virtual machines. It also publishes temporary runtime options for environments that cannot be updated immediately, but those changes can have operational or performance consequences and should be applied only by the responsible administrator under vendor guidance. If suspicious activity is found, preserve logs and coordinate investigation before broad cleanup erases evidence.
AI-assisted reporting disclosure
This article was researched and generated with AI-assisted systems using the Oracle, CERT-EU and Red Hat sources listed below. Dealership Tech Report applies automated accuracy, attribution and risk checks. Vulnerability, version and mitigation statements remain attributed to the named authorities; dealership actions are editorial recommendations, not a forensic finding that any automotive system is affected.
This article reflects advisories checked November 18, 2026. Exposure is conditional and product-specific. The reviewed evidence does not establish that a dealership or automotive vendor uses an affected runtime or has been compromised. Red Hat's build-specific analysis and preliminary score may change, and other Java distributors publish fixes on their own schedules. Mitigation flags can affect performance or supportability; the responsible vendor or administrator should validate them before use.
Cited references
- Oracle — Critical Security Patch Update Advisory, November 2026 — Primary vendor advisory; released Nov. 17, 2026
- CERT-EU — High Severity Vulnerability in Java SE and OpenJDK — National CERT advisory; published Nov. 18, 2026
- Red Hat — CVE-2026-114938 — OpenJDK distributor advisory; checked Nov. 18, 2026
