19 November 2026
Java4Shell: What CVE-2026-114938 means for you
FSP THREAT INTELLIGENCE
Oracle and the OpenJDK project have released fixes for CVE-2026-114938 (Java4Shell), a high-severity flaw in the Base64 decoder of Java that can crash a server and, in some applications, allow unauthenticated remote code execution.
Java is a widely used programming language and software platform that allows applications to run consistently across different operating systems and infrastructure. Organisations commonly use it to build and operate enterprise applications, web services, identity platforms, development tools and server-side systems, including many commercial products that bundle their own Java runtime.
Summary
| The short version Fixed releases are available. Oracle Java SE and OpenJDK 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. GraalVM and OpenJDK distribution builds come from each vendor. CVSS 8.1 (high) from Oracle; the researchers rate it 9.2 (critical) under CVSS 4.0. Exploitation is reported but not confirmed. Vulnerability intelligence feeds logged 3 sightings from 2026-11-18, with no honeypot hits and no successful attacks described by CERTs or the press so far. We assess there is a realistic possibility (40-50%) of targeted exploitation of specific internet-facing Java applications in the next 7 days. Mass, indiscriminate exploitation is less likely, because remote code execution needs particular CPUs and extra attacker work. Do not forget what you do not run yourself. Hosted sites, supplier portals, appliances and container images that bundle their own Java runtime are where unpatched copies tend to hide. |
| CVE | CVSS | Severity | KEV | Published |
| CVE-2026-114938 | 8.1 | HIGH | no | 2026-11-17 |
What happened
Researchers at Calif disclosed CVE-2026-114938, a memory-corruption flaw in the Base64 decoder of OpenJDK, on 2026-11-17. Oracle and the OpenJDK project released fixes for this high-severity vulnerability, which can lead to unauthenticated Remote Code Execution. CISA issued an advisory urging immediate patching, and CERT-EU recommended updating affected versions, prioritising internet-facing applications.
Only x86-64 servers whose CPUs support AVX-512 VBMI run the faulty code; ARM64 is not affected. Any Base64 value an application decodes can carry the trigger. The researchers report unauthenticated remote code execution in default configurations of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate.
| CVE | Product | Affected versions | Fixed in |
| CVE-2026-114938 | Oracle Java SE 8 (performance builds) | 8u511-perf | 8u513 |
| CVE-2026-114938 | Oracle Java SE / OpenJDK 17 | 17.0.6 to 17.0.21 | 17.0.21.1 |
| CVE-2026-114938 | Oracle Java SE / OpenJDK 21 | 21.0.13 and earlier | 21.0.13.1 |
| CVE-2026-114938 | Oracle Java SE / OpenJDK 25 | 25.0.5 and earlier | 25.0.5.1 |
| CVE-2026-114938 | Oracle Java SE / OpenJDK 27 | 27.0.1 and earlier | 27.0.1.1 |
| CVE-2026-114938 | Oracle GraalVM for JDK 17 and 21 | 17.0.21 and 21.0.13 | Oracle November 2026 CSPU |
| CVE-2026-114938 | Oracle GraalVM Enterprise Edition | 21.3.20 | Oracle November 2026 CSPU |
| CVE-2026-114938 | OpenJDK distributions | Builds of the versions above | Each vendor’s fixed build |
Exploitation and honeypot telemetry
Vulnerability intelligence feeds have reported 3 exploitation sightings of CVE-2026-114938, the first on 2026-11-18. These are not yet confirmed: no honeypot sightings are recorded, and CERT and press reporting so far describes no successful attacks. Coverage peaked at 9 articles on 2026-11-18.
- Status: exploitation reported by vulnerability intelligence feeds, not yet confirmed.
- First exploitation signal recorded on 2026-11-18.
- Shadowserver honeypots: no exploitation attempts tagged with these CVEs yet. Sensor networks need a signature before they can label traffic, so this is not evidence that no attacks are taking place.

Figure 1: Reports, advisories and honeypot sightings per day for Java4Shell
Each bar counts items our platform correlated with these CVEs on that day.
| Our assessment We assess there is a realistic possibility (40-50%) of targeted exploitation of specific internet-facing Java applications in the next 7 days. Confidence: Moderate. Crashing an affected JVM is trivial and the trigger is public, and the researchers report unauthenticated remote code execution in default configurations of several widely used products. Against that, code execution needs heap grooming and a separate memory leak, only some x86-64 CPUs are affected, and VulnCheck and watchTowr do not expect indiscriminate exploitation. |
Internet landscape
Java runtimes rarely reveal their version to passive scanning, so our platform cannot count exposed hosts for this vulnerability. Exposure is best judged from your own inventory: which internet-facing applications run on Java, which runtime they use, and whether the servers have AVX-512 capable x86-64 CPUs.
What to do now
Patch first
- Update Oracle Java SE and OpenJDK to 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and GraalVM to the builds in Oracle’s November 2026 Critical Security Patch Update. For Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine and Red Hat builds, take each vendor’s fixed release. Start with internet-facing applications.
- Restart every JVM after patching so the fixed runtime is actually loaded.
- Applications that bundle their own runtime, such as Jira, Confluence, Jenkins, Keycloak, appliances and container images, need their vendor’s update or a rebuilt image.
Reduce exposure while you patch
- If you cannot patch at once, disable the Base64 intrinsic with -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics, or limit the JVM to AVX2 with -XX:UseAVX=2 (CERT-EU). Both need a restart, and the second may cost performance.
- Restrict access to systems you cannot patch at once: VPN, allow-lists or authentication in front of them.
- Validate and size-limit Base64 input at the application boundary, and turn on web application firewall rules where your provider has published them; treat these as stopgaps, not a fix.
- Where none of these is possible, consider taking the system offline or isolating it.
Hunt for signs of compromise
- Review logs on exposed systems for unusual requests, errors and unexpected JVM crashes (hs_err_pid files) since 2026-11-17.
- Check for new or modified files in application and upload directories, and for unexpected child processes of Java services.
- Watch for outbound connections from these systems to unfamiliar hosts, and for new scheduled tasks or accounts.
Look beyond your own servers
- Inventory the Java runtimes you do not host yourself: hosted websites, SaaS, appliances and container images.
- Ask key suppliers and hosting providers whether they are affected and when they will patch, and record the answers.
Sources
| Published (UTC) | Source | Title |
| 2026-11-17 12:00 | CISA | Critical Java Vulnerability Requires Immediate Patching https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching |
| 2026-11-17 22:24 | CyberScoop | A vulnpocalypse bug worthy of attention: Researchers disclose critical flaw in Java with help of AI https://cyberscoop.com/java4shell-critical-java-flaw-openjdk/ |
| 2026-11-18 00:00 | The Record from Recorded Future News | CISA warns of ‘Java4Shell,’ an AI-found Java bug touching most of the Fortune 500 https://therecord.media/cisa-issues-java4shell-alert |
| 2026-11-18 00:00 | CERT-FR | Vulnérabilité dans Oracle Java SE (18 novembre 2026) https://www.cert.cyber.gouv.fr/alerte/CERTFR-2026-ALE-016/ |
| 2026-11-18 00:00 | CERT-FR | Multiples vulnérabilités dans Oracle Java SE (18 novembre 2026) https://www.cert.cyber.gouv.fr/avis/CERTFR-2026-AVI-1562/ |
| 2026-11-18 07:43 | SecurityWeek | Java4Shell Vulnerability Puts Many Enterprise Applications at Risk of Takeover https://www.securityweek.com/java4shell-vulnerability-puts-many-enterprise-applications-at-risk-of-takeover/ |
| 2026-11-18 08:41 | Hackread | Java4Shell Flaw Lets Attackers Target Java Servers Without Logging In https://hackread.com/java4shell-flaw-run-code-java-servers-logging-in/ |
| 2026-11-18 08:47 | SecurityWeek | Oracle Patches 640 Vulnerabilities With November 2026 CSPU https://www.securityweek.com/oracle-patches-640-vulnerabilities-with-november-2026-cspu/ |
| 2026-11-18 10:11 | CERT-EU | 2026-021: High Severity Vulnerability in Java SE and OpenJDK https://cert.europa.eu/publications/security-advisories/2026-021/ |
| 2026-11-18 10:45 | Security Affairs | 65 Characters to RCE: Inside the Java4Shell Vulnerability https://securityaffairs.com/203387/hacking/65-characters-to-rce-inside-the-java4shell-vulnerability.html |
| 2026-11-18 11:12 | Help Net Security | Java4Shell OpenJDK flaw: Exploitation is tricky and hinges on specific CPUs (CVE-2026-114938) https://www.helpnetsecurity.com/2026/11/18/java4shell-openjdk-vulnerability-cve-2026-114938/ |
| 2026-11-19 02:39 | Zscaler ThreatLabz | CVE-2026-114938: OpenJDK Base64 Decoder Vulnerable To Pre-Authentication RCE (Java4Shell) https://www.zscaler.com/blogs/security-research/cve-2026-114938-openjdk-base64-decoder-vulnerable-pre-authentication-rce |
| 2026-11-17 | CVE record | CVE-2026-114938 reference https://www.oracle.com/security-alerts/cspunov2026.html |
| 2026-11-17 | CVE record | CVE-2026-114938 reference http://www.openwall.com/lists/oss-security/2026/11/17/31 |
| 2026-11-17 | CVE record | CVE-2026-114938 reference https://calif.io/java4shell |
Platform statistics are aggregate counts from our platform’s passive observations of internet-facing systems and do not identify any organisation. Judgements use the Professional Head of Intelligence Assessment (PHIA) probability yardstick. This advisory reflects information available on 19 November 2026.
Concerned about your exposure?
Speak to our cyber experts for advice and support