A memory-corruption bug in the Java runtime has drawn an urgent alert from CISA. On 17 November the agency, working with the Canadian Centre for Cyber Security, told organisations to find and patch Oracle Java installations affected by CVE-2026-114938, a flaw in the Base64 decoder of the x86-64 HotSpot virtual machine that CISA’s alert calls “Java4Shell”. Because Java sits inside a vast amount of enterprise software, often invisibly, the hard part of this fix is not applying a patch but knowing where the runtime lives.
What the agencies and Oracle have said
CISA’s alert describes the issue in plain terms: Base64 data built in a particular way can corrupt memory in the JVM, crash it, and in the agency’s assessment open the door to remote code execution by an attacker who needs no credentials. The vulnerable code is part of the Java Development Kit, so it ships wherever a JDK or Java runtime does.
The CVE record, published by Oracle as the numbering authority later the same day, fills in the scoring. Oracle rates the flaw 8.1 under CVSS 3.1, which is High rather than Critical, with the vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. In practice that means network-reachable and unauthenticated, but rated hard to pull off, with full loss of confidentiality, integrity and availability if an attack succeeds. Oracle files the bug under the Java SE “Compiler” component and states that it is reachable when untrusted data is passed to the affected APIs, for example by a web service, rather than through untrusted applets or Java Web Start applications. CISA’s enrichment of the record classifies the weakness as a heap-based buffer overflow (CWE-122).
The record lists these supported releases as affected:
| Product | Affected versions |
|---|---|
| Oracle Java SE | 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 |
| Oracle GraalVM for JDK | 17.0.21.0.3, 21.0.13.0.3 |
| Oracle GraalVM Enterprise Edition | 21.3.20.0.3 |
Neither the alert nor the record names the fixed builds; both point to Oracle’s November 2026 Critical Security Patch Update advisory for patching guidance.
What is not known yet
Neither CISA’s alert nor the CVE record reports exploitation. CISA’s own SSVC assessment in the CVE record, dated 17 November, scores exploitation as “none”, automation as “no”, and technical impact as “total”. The CVE is not in the Known Exploited Vulnerabilities catalog. The alert does not say why CISA chose to issue it ahead of any reported exploitation, and it says nothing about whether a working attack has been shown publicly, which specific APIs that expose the decoder, or whether OpenJDK builds from other distributors carry the same code. Readers running non-Oracle JDKs should watch their own vendor’s channel rather than assume they are clear.
There is also a gap between the two descriptions of difficulty. CISA’s alert stresses unauthenticated code execution; Oracle’s score marks attack complexity as high. Both can be true: a crash may be easy to trigger while reliable code execution is not. Plan for the denial-of-service case at minimum.
Where the exposure sits
The alert warns that inventories may undercount this. Java runtimes often arrive inside something else: a vendor application with its own bundled JRE, a container base image, a network or storage appliance. None of those necessarily appears as “Java” in an asset list. Any service that accepts Base64 from outside, which covers a wide range of web APIs, file uploads and message formats, is the place to look first.
What to do, in order
- Find the runtimes. Search hosts, images and appliance documentation for JDK and JRE installs, including copies embedded in third-party products. Check container registries for base images built on affected releases.
- Patch internet-facing systems first. Apply Oracle’s update, or the update from whichever vendor ships your runtime, as soon as it is available, starting with anything reachable from the internet that parses Base64.
- Ask appliance and software vendors directly. Where Java is bundled, you depend on the vendor to ship a fixed build. Ask for a date.
- Use compensating controls where you cannot patch yet. CISA suggests validating and restricting Base64 input at the application edge, capping input size, and cutting back unauthenticated access to affected services.
- Watch for signs of trouble. Unexpected JVM crashes, Java processes you cannot account for, and runtimes that should not be there are all worth investigating, per the alert.
Frequently Asked Questions
What is CVE-2026-114938? It is a memory-corruption flaw in the Base64 decoder of Oracle’s x86-64 HotSpot JVM. CISA warns that crafted input can crash the JVM and may allow unauthenticated remote code execution.
Is CVE-2026-114938 being exploited? No exploitation had been reported as of 17 November. CISA’s assessment in the CVE record scores exploitation as none, and the flaw is not in the KEV catalog.
Which Java versions are affected by CVE-2026-114938? The CVE record lists Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus specific GraalVM for JDK and GraalVM Enterprise Edition releases. Oracle’s November 2026 advisory has the patching guidance.
Source: Cybersecurity and Infrastructure Security Agency (CISA)