Skip to main content

Researchers disclose critical OpenJDK Base64 flaw found with AI assistance

18 NOVEMBER 2026·2 MIN READ·5 SOURCES

Researchers published details Tuesday of a critical Java vulnerability tracked as CVE-2026-114938 and nicknamed Java4Shell. The flaw is in OpenJDK’s Base64 decoder, and Oracle shipped patched Java builds Tuesday afternoon.

Researchers disclose critical OpenJDK Base64 flaw found with AI assistance

Key takeaways · 4

  • 01

    Check Java installations and bundled runtimes, then prioritize patching: CISA strongly urges organizations to patch, and OpenJDK recommends upgrading affected versions.

  • 02

    The disclosed trigger is 64 “A” characters followed by “=”; the malformed input can make the decoder write 64 bytes into a buffer that may hold only 50.

  • 03

    Do not assume every system is affected: the optimization runs only on chips supporting AVX-512, and ARM64 systems are unaffected.

  • 04

    If immediate patching is not feasible, CISA recommends restricting and validating Base64 input, enforcing input-size limits and limiting unauthenticated access.

A decoder flaw with severe potential impact

Calif describes Java4Shell as a memory-corruption vulnerability in OpenJDK’s Base64 decoder.[2] The corruption can be triggered by 64 “A” characters followed by “=”, and the malformed input can make the decoder write 64 bytes into a buffer that may hold only 50.[2][1] CISA says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution; CyberScoop reports Calif said the corruption can be turned into control of the server.[4][1] The reported CVSS ratings differ: Calif gives it 9.2 out of 10 under CVSS 4.0, while OpenJDK lists a score of 8.1.[2][3]

Exposure depends on system configuration

CyberScoop reports that the optimization involved runs only on chips supporting AVX-512, and that ARM64 systems are unaffected.[1] Calif also says a Java program can be compromised by connecting to a malicious server, even if the program exposes no service.[2] Those details make it important to look beyond public-facing services when checking where Java runs.

Patches and interim safeguards

Oracle shipped patched Java builds Tuesday afternoon.[1] OpenJDK lists affected versions as 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33, 8u512 and earlier, and recommends upgrading.[3] CISA strongly urges organizations to patch and recommends inventorying Java installations, including runtimes bundled with third-party software, container images and appliances.[4] If an immediate patch is not feasible, CISA recommends temporary controls: restrict and validate Base64 input, enforce input-size limits and limit unauthenticated access.[4]

AI-assisted discovery, with limits

According to CyberScoop, Calif researcher Quang Luong found the bug in about an hour using OpenAI’s Codex; Calif says the total token cost was less than $200.[1][2] Calif says most later exploit chains were built almost autonomously with AI, but also says there is no universal exploit.[2] Calif withheld product-specific exploit details to give users time to upgrade.[1] CyberScoop reported that no exploitation in the wild had been reported as of publication and that the CVEs had not been added to CISA’s Known Exploited Vulnerability list.[1] That status is not a reason to defer patching: CISA urges organizations to act.[4]

Java may be present in runtimes bundled with other software, so teams should include those deployments in their inventory and patch planning. The reported attack path and severe potential impact make interim input controls useful where upgrades cannot happen immediately.

Why it matters
For teams

AI training for your team

kju.ai is built for teams: daily sessions, team analytics, and rollout support for your organization.

How this developed

  1. 18 November 2026

    Researchers disclose critical OpenJDK Base64 flaw found with AI assistance

Sources

AI fluency, one session a day, built for your work.