Security News

Java4Shell: Critical OpenJDK Flaw Found With AI Could Let Attackers Take Over Servers

CyberScoop · 18 Nov 2026
Key Takeaway Find out which of your servers and business applications run Java, and apply the patched OpenJDK or Oracle Java builds as soon as you can.

Security researchers have published details of a critical flaw in Java that could let an attacker take over a server without a password. Tracked as CVE-2026-114938 and nicknamed Java4Shell, the bug sits in the Base64 decoder of OpenJDK, the free Java runtime used across banking, aviation and telecommunications. Calif Research rated it 9.2 out of 10 on the CVSS scale, which counts as critical.

It is a memory-corruption bug. In a specific case, the decoder writes 64 bytes into a buffer that may hold as few as 50, damaging the memory next to it. The faulty code is a speed optimisation that runs only on chips supporting AVX-512; ARM64 systems are unaffected. Calif says an attacker needing no login could corrupt memory, read nearby data in a way similar to Heartbleed, and escalate to full control.

The group reported unauthenticated code execution in products including Keycloak, Jira, Confluence, Jenkins and PingFederate, and demonstrated a working break-in against Keycloak. Authenticated execution was shown in Kafka, Solr and Elasticsearch. Calif says there is no universal exploit, as each target needs tailored steps, and it is withholding product-specific details until users have time to upgrade.

AI played a large role. Calif says researcher Quang Luong found the bug in about an hour using OpenAI's Codex for under $200 in tokens, and AI agents produced most of the exploit chains almost unaided. OpenJDK published an advisory and Oracle shipped patched builds on the same Tuesday, and CISA issued a notice urging patching. No exploitation in the wild had been reported at publication, but researchers told CyberScoop that real-world attacks are likely. Oligo Security's Gal Elbaz urged compensating controls while patches roll out.

Why it matters

Many businesses do not know Java sits underneath tools like Jira, Confluence, Jenkins and Keycloak, so a runtime flaw can expose systems no one tracks as 'Java'. The Keycloak demonstration matters because login systems are trusted gatekeepers, and a pre-authentication bug bypasses the password control entirely. With AI cutting discovery and exploit development to hours, the usual grace period between disclosure and attack is likely to be shorter.

What to do

  • Apply the patched OpenJDK or Oracle Java builds released Tuesday to all servers running Java.
  • Inventory internet-facing products such as Keycloak, Jira, Confluence, Jenkins and PingFederate, and patch them first.
  • Check whether your servers use AVX-512 capable processors, since ARM64 systems are unaffected.
  • Add compensating controls that block exploitation attempts until patching is complete.
Java OpenJDK CVE-2026-114938 Java4Shell AI-assisted vulnerability research Patch management

Summarised by CISO AI from CyberScoop, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.