0
Skip to content

CISA Urges Immediate Patching of Critical Java Flaw

java coding codeOfficials say a memory-corruption bug in Java’s Base64 decoder could let attackers run code without logging in, and Oracle has released fixes.

11/18/2026 3:30 P.M.

The Cybersecurity and Infrastructure Security Agency (CISA) is urging organizations to immediately patch a critical Oracle Java vulnerability that could allow unauthenticated remote code execution. The New York State Department of Financial Services (NYDFS) issued its own alert to regulated entities Wednesday.

The flaw, tracked as CVE-2026-114938 and nicknamed “Java4Shell,” affects the Base64 decoder in the x86-64 HotSpot Java Virtual Machine (JVM), which is part of the Java Development Kit.

CISA said specially crafted Base64 input can crash the JVM and let an attacker execute code remotely. Oracle, which maintains Java, released patches for the vulnerability Nov. 17, according to TechRadar.

The security firm Calif discovered the bug and published a technical breakdown the same day.

“Java is the world’s third most popular programming language, powering 90% of Fortune 500 companies,” Calif said in its report. “It is the beating heart of the modern economy. Banking, aviation, telecommunications, nearly every critical sector runs on Java, including national security systems.”

Oracle’s advisory lists Java SE 8 (the 8u511b33-perf build), 17, 21, 25 and 27, along with Oracle GraalVM for JDK 17 and 21 and GraalVM Enterprise Edition 21.3. Java 11 is not listed for this vulnerability. Oracle said it can be exploited by supplying data to the affected APIs, such as through a web service.

Oracle rated the flaw 8.1 out of 10 for severity, while Calif, the firm that found it, rated it 9.2.

Oracle’s advisory notes that it continues to receive reports of attempts to exploit vulnerabilities it has already patched, and that some attackers succeeded because customers had not applied available patches.

What CISA Recommends

  • Identify affected installations. CISA noted that JDKs and Java runtimes may not appear as separate entries in software inventories, particularly when bundled with third-party applications or included in container images and appliances.
  • Apply Java and vendor patches, starting with internet-facing systems.
  • If patching must wait, restrict and validate Base64 input at the application boundary, enforce input-size limits and limit unauthenticated access.
  • Monitor for rogue runtimes, unexpected JVM crashes, and suspicious Java processes.

New York Regulator Issues Parallel Alert

NYDFS told its regulated entities that Java is embedded in many software applications and hardware devices, so it “may be present in more places than organizations expect.” The department urged them to identify and fix affected JDKs and runtimes quickly, including those bundled with third-party applications, container images, and appliances.

DFS also told regulated entities to work with internal development teams and third-party software providers to confirm whether affected Java versions are present and whether patching or other mitigation is in place.

Java often runs inside software that agencies buy rather than build. Members should ask software vendors directly whether their products bundle a vulnerable Java runtime and when fixed versions will ship.

 

Remember to subscribe to ACA Daily and Member Alerts under your My ACA Assistant profile when logged in to acainternational.org. 

If you have executive leadership updates or other member news to share with ACA, contact our communications department at comm@acainternational.org. View our publications page for more information and our news submission guidelines here.

One moment please...

Share Profile

This site utilizes cookies as included in our Privacy Policy and User Agreement.