Java4Shell: AI-found Java flaw CVE-2026-114938 patched; what to update

Representative image: rupixen / Pixabay
Security firm Calif used AI to find Java4Shell, a remote code execution flaw in Java 17, 21, 25 and 27; Oracle and OpenJDK shipped fixes on 17 November 2026.
Java4Shell: what happened
A serious security flaw in Java, nicknamed Java4Shell and tracked as CVE-2026-114938, was disclosed on Tuesday, 17 November 2026, the same day Oracle and the OpenJDK project released fixes. The flaw was found by Calif, a security firm that says it used artificial intelligence (AI) in its research. It sits in the part of Java that decodes Base64 data and, on some processors, can let an attacker run their own code on a server without logging in. Switzerland's national cyber security agency issued an alert the same day.
Java4Shell: key facts
- Name and ID: Java4Shell, CVE-2026-114938.
- Disclosed and patched: Tuesday, 17 November 2026, alongside Oracle's November 2026 Critical Patch Update, which carries 11 new patches for Java SE.
- Found by: security firm Calif, whose researchers are credited in Oracle's update; Calif says AI helped it find the flaw.
- What it is: a memory-corruption bug (a heap out-of-bounds write) in OpenJDK's hardware-accelerated Base64 decoder, which can allow remote code execution without authentication.
- Affected: Java 17, 21, 25 and 27; Java 8 and 11 are generally not affected, though Oracle lists one Java 8 performance build as affected. The risk depends on servers running on processors with AVX-512 instructions.
- Severity: Oracle and OpenJDK rate it 8.1 under CVSS 3.1; Calif rates it 9.2 under CVSS 4.0.
- Exploitation: none had been reported as of 17 November.
Java4Shell: why it matters
Java runs a huge share of the world's business software: banking systems, government portals, e-commerce back-ends and the internal tools of most large companies, including India's IT services firms and their clients. A flaw that lets an outsider run code on a Java server without a password is among the most serious kinds of bug, which is why the nickname deliberately echoes Log4Shell, an earlier flaw in a Java logging library that set off a worldwide rush to patch.
Base64 is a common way to turn binary data, such as images or keys, into plain text so it can travel inside web requests. Because so many applications decode Base64 data that arrives from users, a bug in Java's own decoder can be reached from outside in many setups. The flaw is in a faster version of the decoder that uses special instructions on newer processors, called AVX-512, which is why the processor matters.
The way the bug was found is also news. Security firms and AI labs have been racing to show that AI models can find serious flaws in widely used software. Calif's claim that AI helped it uncover Java4Shell is another sign that AI is changing vulnerability research, for defenders and, potentially, attackers. That is a strong reason to patch quickly rather than wait.
There is some uncertainty in the record. One security company noted that early Oracle release notes did not name this CVE, and severity scores differ between Oracle and the researchers. What is not in dispute is that fixed builds are available and that Switzerland's national cyber agency has told operators to check their systems.
Peepals timeline: On 17 November 2026, Oracle published its November Critical Patch Update with 11 Java SE fixes, and Calif disclosed Java4Shell the same day, with OpenJDK releasing patched builds. Also on 17 November, Switzerland's National Cyber Security Centre issued an alert urging operators to check their systems. As of that date no attacks using the flaw had been reported.
| Item | Detail |
|---|---|
| CVE | CVE-2026-114938 (Java4Shell) |
| Affected Java versions | 17, 21, 25, 27 |
| Generally not affected | Java 8, 11 |
| Severity | 8.1 (Oracle, CVSS 3.1); 9.2 (Calif, CVSS 4.0) |
| Fix released | Tuesday, 17 November 2026 |
Java4Shell: impact
Short-term: Companies running Java 17, 21, 25 or 27 need to find every Java runtime they use, including those bundled inside other products, and install the November updates.
Long-term: If AI keeps speeding up the discovery of deep flaws in core software, patch cycles will have to get faster, and start-ups selling AI-driven security research are likely to grow.
Who is affected: Developers and IT teams in banks, government agencies, start-ups and IT services firms that run Java servers; software vendors whose products bundle Java; and security teams in India and abroad.
What to watch next: Whether attacks using the flaw are reported, and whether India's CERT-In issues its own advisory.
Java4Shell: key takeaway
If your organisation runs Java 17 or later, list every Java runtime, including those bundled in other software, and install Oracle's or your OpenJDK vendor's November 2026 update now.
Java4Shell: questions and answers
What is Java4Shell?
Java4Shell is the nickname for CVE-2026-114938, a flaw in Java's hardware-accelerated Base64 decoder that can let an attacker run code on a server without logging in.
Which Java versions are affected by Java4Shell?
Java 17, 21, 25 and 27 are affected; Java 8 and 11 are generally not, apart from one Java 8 performance build Oracle lists.
Has Java4Shell been used in attacks?
No exploitation had been reported as of 17 November 2026, the day the flaw was disclosed and patched.
Who found Java4Shell?
Security firm Calif found it and says AI helped its research; Oracle's patch update credits Calif's researchers.
Disclaimer: Prepared by the Peepals newsroom from publicly available sources with AI assistance. Information is accurate to the best of our knowledge at the time of publication and may change. Images may be representative. Not professional advice. Report an error via our contact page.
By Karan Bansal, Tech Startups CorrespondentCovers Tech Start-ups & Stories and more for Peepals Tech. All stories by Karan Bansal
Sony wins UK PlayStation Store case: £1.97 billion claim dismissed
Karnataka AI skilling: Google, Sarvam, three others to train 63,200
Your week ahead, every Sunday. Free.
Exam and result dates, IPOs opening, scheme deadlines, government holidays and the RBI decision for the next 7 days, plus the week's top stories. One email a week, unsubscribe in one click.
Karan Bansal is a pen name of the Peepals Global Editorial Team, which researches, fact-checks and publishes every story. The portrait is an illustration.
Responsible for this story: the Peepals Global Editorial Team, led by editor Prashant Sonar. How we report









