Oracle’s November 17 Java security update addresses CVE-2026-114938, a network-reachable flaw that Oracle’s CVE record says can let an unauthenticated attacker take over affected Java SE and GraalVM runtimes. It names specific builds in three Oracle product lines. For teams running Java services, the immediate job is to find those builds in the processes that actually serve requests, then update them.

Sophos X-Ops calls the issue Java4Shell and says crafted Base64 input can crash a JVM or enable remote code execution. Sophos locates the defect in the x86-64 HotSpot Base64 decoder; Oracle’s CVE record names the Compiler component and also lists GraalVM products. Use Oracle’s affected-product list for inventory rather than narrowing the search to the decoder description. Sophos reported no active exploitation at publication.

Network data reaches Java APIs

Oracle describes an unauthenticated network attacker supplying data to APIs in the named component, including through a web service. The attack uses multiple possible protocols and has high attack complexity. It does not require an untrusted Java Web Start application or an untrusted applet. Oracle puts the consequence plainly: “Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition.” Oracle scores it 8.1 under CVSS 3.1; successful exploitation could expose data, alter application behavior or stop the service.

Sophos’s Base64 finding gives application owners a useful place to start: internet-facing x86-64 services that decode untrusted Base64 input. A web endpoint may pass client-supplied data into Java without exposing the Java process directly. The affected component description differs between the two primary accounts, so a search for Base64 handlers alone would miss the wider Oracle inventory decision. Trace the deployed service to its loaded runtime, including runtimes shipped inside application images and separately installed GraalVM environments.

Match builds to affected products

The NVD record reproduces Oracle’s affected-build list. For Oracle Java SE, it lists 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. For Oracle GraalVM for JDK, it lists 17.0.21.0.3 and 21.0.13.0.3. For Oracle GraalVM Enterprise Edition, it lists 21.3.20.0.3. Those are affected builds; treat them as matches to replace, not as target patch versions.

Start with the runtime used by each network-facing service, then check the rest of the Oracle Java and GraalVM estate against that list. Compare the running process’s runtime identity and build with the packaged runtime and the version planned for rollout: a host-level java on an administrator’s path can differ from the binary inside a container or application bundle. Record the service, runtime vendor, product, build and exposure path together so an updated host package cannot be mistaken for an updated application process.

For each affected service, check whether unauthenticated network input reaches its Java runtime through any exposed service ingress route, including a web endpoint. Record the ingress route and the loaded build before ranking the rollout.

Patch the running services first

Sophos says Oracle released November 2026 updates and recommends prioritizing internet-facing x86-64 services that decode untrusted Base64. Apply the relevant Oracle security update to the runtime used by those services, restart or redeploy the application, and then work through the remaining affected Oracle builds. Choose the fixed replacement for each product and branch from Oracle’s November advisory, linked in its CVE record. Verify the target release before rollout; the build strings above identify versions to replace.

Sophos relays Oracle’s general interim advice to block the network protocols an attack requires. Oracle labels the protocol for this CVE “Multiple,” and Sophos warns that protocol blocking can break application functionality. If patching must wait, restrict the specific service’s untrusted network input at its existing ingress control and test the application path that restriction changes. Patch the affected runtime after any interim ingress restriction.

Sophos is still assessing detection countermeasures. Use crash reports and existing service and ingress logs to investigate unusual behavior if an affected service was exposed; an ordinary JVM crash alone is not an exploit signature.

Verify the deployed Java build

After redeployment, inspect the runtime build inside the running application process or container and compare it with the product-specific fixed release in Oracle’s advisory. Confirm the exposed service is using that build, then exercise its normal request path to catch regressions from an interim ingress restriction. If the old affected build is still loaded, the service still needs a restart or a corrected image. The version running in the service, rather than the version installed elsewhere on its host, decides whether this update reached the code taking requests.