Java4Shell inventory includes containers and bundled JVMs
The patched host is not always the patched application. CVE-2026-114938 lives in Java runtime code, and many production services carry a JVM inside a container image, application package, or appliance. A package inventory that checks only the operating system can miss the runtime that actually executes the vulnerable decoder.
Oracle rates the vulnerability 8.1 under CVSS 3.1. CISA urges immediate patching and specifically notes that JDKs and Java runtimes may be bundled in third-party applications, container images, and appliances. The warning fits the deployment model of modern Java services.
The inventory gap
A Linux image can use a patched OpenJDK package while a service starts /opt/application/jre/bin/java from an older vendor distribution. A container can contain both a system runtime and a bundled runtime. An orchestration platform can report the image digest but not the Java build inside it.
The same split appears during updates. Rebuilding an application image does not guarantee a new JVM if the Dockerfile copies a cached runtime layer or downloads a pinned archive. A host patch can fix the host process while leaving the container image unchanged.
What to record
For every Java service, capture the executable path, java -version, distribution vendor, full build string, container image digest, and the node or virtualization layer where it runs. Add CPU feature evidence from that execution environment. Record the effective intrinsic and AVX settings.
Where the application exposes a management interface, jcmd can identify the running process and flags. A host-level scan can locate candidate Java binaries, but it does not show which binary serves traffic. Correlate the runtime with the listening process and deployment identity.
Mechanism and impact
The vulnerable path is the x86-64 HotSpot AVX-512 VBMI Base64 intrinsic. Malformed padding can underflow an output length and write beyond the decode buffer. The JVM may reject the input afterward, but the heap write occurs inside the native path first.
A crashed container may restart automatically, which can hide a repeated denial of service. A successful exploit would inherit the container's service account, mounted secrets, network policy, and filesystem access. The blast radius depends on the pod and node isolation around that process.
Affected products and scope
Oracle lists affected Java SE and GraalVM builds, including the Java SE 8u511b33-perf build. CERT-EU maps upstream OpenJDK fixes to 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1. OpenJDK-derived distributions publish their own fixed build identifiers. Red Hat says standard OpenJDK 8 and 11 do not contain this vulnerable intrinsic, but other security updates still apply.
Exposure context
A ZoomEye query based on Confluence, Jira, Jenkins, Artifactory, Keycloak, and PingFederate fingerprints returned 252,557 product matches on November 18, 2026. An exact CVE lookup returned 0. The Search figure can guide application discovery. It cannot prove that a matching service uses an affected JVM or runs on eligible hardware.
Remediation
Replace the vulnerable runtime in the build artifact and the deployed instance. Restart the service, then verify the runtime from inside the running container or process. Do not infer success from a changed image tag alone.
If immediate replacement is impossible, disable the Base64 intrinsic or AVX-512 path where the x86-64 conditions apply. Restart the process and confirm the setting. Limit unauthenticated access and validate Base64 input as additional controls.
Update autoscaling templates, disaster recovery images, batch workers, and occasional administrative containers in the same change set. A fleet can appear patched while an old image remains available for rollback or burst capacity. Track the JVM build as part of the deployment inventory so the next runtime vulnerability does not repeat the same discovery delay.
Top comments (0)