1-minute read
What a defender needs to know
Oracle’s November 17 Java update addresses CVE-2026-114938, a flaw that Oracle’s CVE record says an unauthenticated network attacker could use to take over affected Oracle Java SE, GraalVM for JDK or GraalVM Enterprise Edition runtimes. Oracle lists eight affected builds across those three product lines; NVD reproduces the list. The CVSS 3.1 base score is 8.1 and exploitation is described as difficult.
Sophos calls the issue Java4Shell and points to the x86-64 HotSpot Base64 decoder, while Oracle names the Compiler component and includes GraalVM. Scope the inventory by Oracle’s affected products rather than only by Base64 handlers. Prioritize internet-facing x86-64 services that decode untrusted Base64, then work through other affected Oracle deployments. Sophos reported no active exploitation when it published.
Find the runtime loaded by each affected service or container and apply the relevant November Oracle update. Verify the build inside the running process against the fixed release for its product in Oracle’s advisory; an updated host package may leave a bundled runtime untouched. If a rollout must wait, restrict untrusted network input to the service at its ingress point and test the affected application path. Protocol blocking may break functionality, and Oracle lists multiple possible protocols for this flaw. Record each service’s loaded Oracle product, build and network input route. After redeployment, exercise the normal request path and confirm that the serving process uses the replacement runtime build.