Java4Shell Vulnerability CVE-2026-114938: Critical OpenJDK Base64 Flaw, Attack-Shaped Traffic Recorded, and What to Patch This Week
Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in OpenJDK's Base64 decoder. It affects unpatched builds from 17.0.6 onward. Patches are out, and GreyNoise has logged requests shaped like the attack.
Where Worldwide
On this page 8 sections
A critical flaw in Java, nicknamed Java4Shell and tracked as CVE-2026-114938, was disclosed on November 17, 2026. Oracle and the OpenJDK project released patches the same day. If your business runs software built on Java, whether that is an in-house web app, an Elasticsearch cluster or Red Hat Enterprise Linux servers, update the Java behind it this week. Traffic that matches the shape of a Java4Shell attack has already been recorded.
Below is what is confirmed, what is not known, and a checklist you can work through.
What is Java4Shell (CVE-2026-114938)?
Java4Shell is a critical memory-corruption vulnerability in the Base64 decoder of OpenJDK, the Java runtime that many vendors build and ship. Base64 is a common way of turning data into plain text, and the decoder is the part of Java that turns it back.
Qualys says unpatched OpenJDK builds from 17.0.6 onward are affected, whichever vendor built them. So the brand on your Java install does not protect you. What matters is the version and whether the patch is installed.
Calif disclosed the bug on November 17, and Oracle and the OpenJDK project released patches that day. As of November 17, 2026, Amazon had also released Corretto 17.0.21.1.2 with the fix.
How serious is Java4Shell?
The published scores differ:
| Who rated it | Rating | Scale |
|---|---|---|
| The researchers who found it | 9.2 | CVSS v4.0 |
| Oracle | 8.1 | CVSS v3.1 |
| Red Hat | Critical | Red Hat's own rating |
The two numbers come from different versions of the CVSS scoring system, so you cannot compare them directly. Even so, every rating above is high enough that this belongs on this week's patch list.
Is Java4Shell being exploited? What is confirmed and what is not
What our sources confirm:
- GreyNoise had recorded over 150 requests matching the shape of a Java4Shell attack, coming from five IP addresses.
- Cisco's product security team knows of proof-of-concept exploit code but has no knowledge of malicious use.
What is not known:
- Whether any of those requests actually worked against a real system.
- Who sent them, or which applications they targeted.
- What an attacker can do once the flaw is triggered. Our sources call it memory corruption but do not describe the end result, and we will not guess.
- Whether any organisation has been breached through it.
Here is the careful reading: attack-shaped traffic exists, proof-of-concept code exists, and our sources report no confirmed break-ins.
Which products are affected by Java4Shell?
Vendors are publishing their own advisories. Here is what each one says, as reported:
| Product or vendor | What is reported |
|---|---|
| OpenJDK builds, any vendor | Unpatched builds from 17.0.6 onward are affected |
| Amazon Corretto | Corretto 17.0.21.1.2 released with the fix |
| Oracle Java | Patch released November 17, 2026 |
| Red Hat Enterprise Linux | Rated Critical, RHEL 8, 9 and 10 affected |
| Elasticsearch | Every release from 7.17.3 onward affected, according to Elastic |
| Siemens Industrial Edge Management | Three products affected, according to Siemens |
| Cisco | Aware of proof-of-concept code, no known malicious use |
Our sources leave out several details:
- the fixed Elasticsearch release
- the names of the three Siemens products
- whether Red Hat has shipped fixed packages yet
- the version numbers of the Oracle and OpenJDK patches
- which Cisco products, if any, are affected
Check each vendor's own advisory for these before you mark a system as fixed.
Why Java4Shell matters for a business network
Most owners do not think of their search cluster, their Linux servers or their industrial edge software as Java. That is the trap. The vendor list above shows how far one runtime reaches: an operating system, a search engine and industrial management tools all appear on it.
When Java comes inside someone else's product, that vendor decides when its copy gets updated. Updating Java on your own server does not change a copy packed inside an appliance or a container image.
For websites and web apps the rule is simple. If it runs on an OpenJDK build from 17.0.6 onward and faces the internet, put it near the top of this week's list.
How to check and patch Java4Shell this week
| Step | What to do | How to check |
|---|---|---|
| 1. Find every Java runtime | List the servers, containers and apps that run Java | Run java -version on servers you manage, and ask vendors about appliances |
| 2. Compare versions | Any build from 17.0.6 onward without the November 17 patch is affected | Match the version against your vendor's advisory |
| 3. Amazon Corretto 17 | Update to Corretto 17.0.21.1.2 | java -version should show the new build |
| 4. Oracle Java and other OpenJDK builds | Install the patch released November 17, 2026 | Check the version against the vendor's release notes |
| 5. RHEL 8, 9 and 10 | Follow Red Hat's advisory and install its Java updates | Check Red Hat's advisory for the fixed packages |
| 6. Elasticsearch 7.17.3 and later | Follow Elastic's advisory for the fix | Check the version on every node |
| 7. Siemens Industrial Edge Management | Find the three affected products in Siemens' advisory | If an integrator runs it for you, ask them to confirm |
| 8. Cisco products | Watch Cisco's advisory for affected products and fixes | Match your models against Cisco's list |
| 9. Internet-facing first | Patch public web apps and APIs before internal tools | Your firewall or hosting dashboard shows what is exposed |
After patching, restart the application. A running Java program keeps using the old runtime until it restarts.
Java4Shell questions people are asking
Is Java4Shell being exploited?
GreyNoise recorded over 150 requests from five IP addresses that match the shape of a Java4Shell attack. Cisco knows of proof-of-concept exploit code but no malicious use. Our sources do not confirm any successful attacks.
What versions of Java are affected by Java4Shell?
Unpatched OpenJDK builds from 17.0.6 onward, from any vendor.
Is a specific Java release line affected by Java4Shell?
Our sources say builds from 17.0.6 onward are affected, but they do not split this out by release line. Check your vendor's advisory for your exact version.
Is there a patch for CVE-2026-114938?
Yes. Oracle and the OpenJDK project released patches on November 17, 2026, and Amazon released Corretto 17.0.21.1.2 with the fix.
What is the CVSS score for Java4Shell?
The researchers who found it rate it 9.2 under CVSS v4.0. Oracle rates it 8.1 under CVSS v3.1. Red Hat rates it Critical.
Does Java4Shell affect Elasticsearch?
Yes. Elastic says every Elasticsearch release from 7.17.3 onward is affected.
I never installed Java. Am I safe?
Not necessarily. RHEL 8, 9 and 10, Elasticsearch and three Siemens Industrial Edge Management products are all named as affected, so Java may be running inside products you rely on. Ask your vendors.
The bigger lesson
The runtime under your software is part of your attack surface, even if you never chose it. Keep a list of what runs Java, who updates each copy and how fast they do it. When the next flaw lands, that list decides whether the fix takes hours or a week of searching.
For help finding and patching every Java runtime on your network, see security hardening or request a quote.
Get security alerts like this by email, with the free checklist, at security alerts.
Sources: Qualys: How to find, mitigate and patch the critical Java4Shell flaw CVE-2026-114938; SecurityWeek: Java4Shell exploitation attempts begin as vendors rush out advisories.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
CISA KEV: Apache Axis, REDCap, Synology DSM and LiteLLM Flaws Exploited, No Patch Coming for Axis 1.x, and the Fixed Versions to Install
CISA has added exploited flaws in Apache Axis, REDCap, Synology DSM and LiteLLM to its KEV catalog. Apache wil...
Database RCE: PostgreSQL CVE-2026-116331, ClickHouse, MySQL and Oracle Flaws Show Locked-Down Database Accounts Can Still Reach the Server, and the Fixed Versions
Depthfirst researcher Zheng Yu showed that tight database permissions still leave room for attacks that run co...
VMware vCenter CVE-2026-123890
A critical VMware vCenter flaw, CVE-2026-123890 (CVSSv3 9.8), lets attackers open a vCenter administrator sess...