Have you checked the Java runtime behind your Jira, Confluence, Jenkins and Keycloak?
CVE-2026-114938 is a vulnerability in the Compiler component of OpenJDK and Oracle Java SE. The OpenJDK Vulnerability Advisory of 17 November 2026 and Oracle's November 2026 Critical Security Patch Update both score it CVSS 3.1 8.1 High, with high attack complexity. Successful attacks, the official CVE record says, can result in takeover of the Java runtime. BleepingComputer reports that security researchers call it Java4Shell, describe it as memory corruption in Java's hardware-accelerated Base64 decoder, and say it can lead to unauthenticated remote code execution in default configurations of widely used applications. Upgrade to the 17 November 2026 OpenJDK and Oracle Java SE releases (17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1 in the lines this CVE affects).
Critical by impact (our framing). Vendor score: CVSS 3.1 8.1 High
OpenJDK and Oracle score this CVSS 3.1 8.1 High (vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). BleepingComputer reports that security researchers rate it CVSS 4.0 9.2 Critical. We use Critical by impact as our framing because the official record describes takeover of the Java runtime, and because that report describes unauthenticated code execution in default installs of widely deployed applications. SecurityWeek reported internet-wide probing and blind exploit attempts on 19 November 2026 at 09:10 GMT, including java4shell-recon user-agents and a later return posing as Chrome. Public reporting has not confirmed a successful compromise. The CVE was not in CISA's Known Exploited Vulnerabilities catalogue when we rechecked on 19 November 2026 (catalogue 2026.11.18, released 19:17 GMT on 18 November 2026). CISA's ADP entry on the CVE record, last updated at 22:02 GMT on 17 November 2026, listed Exploitation as "none". That entry predates this reporting, and we do not treat absence from KEV, or that earlier label, as proof that a flaw is unused. Recheck KEV. We do not link proof-of-concept or exploit code.
Updated 19 November 2026. SecurityWeek (09:10 GMT) reports internet-wide probing and blind exploit attempts, including requests with a java4shell-recon user-agent. In one case, a scanner probed with a Java4Shell user-agent, then returned about 17 hours later with the exploit trigger while posing as Chrome. Public reporting has not confirmed a successful compromise. The CVE was not in CISA's Known Exploited Vulnerabilities catalogue when we rechecked on 19 November 2026 (catalogue 2026.11.18). Restart JVMs after you apply a fixed build.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 19 November 2026, 10:09 GMT.
At a Glance
Based on the OpenJDK Vulnerability Advisory of 17 November 2026, Oracle's November 2026 Critical Security Patch Update, the official CVE-2026-114938 record, the NVD copy of that record, BleepingComputer (17 November 2026), SecurityWeek (19 November 2026, 09:10 GMT), vendor advisories from Cisco, Elastic, Atlassian, Jenkins, Keycloak, Siemens, Red Hat, Microsoft and Eclipse Temurin, and CISA's Known Exploited Vulnerabilities catalogue, rechecked on 19 November 2026 (catalogue 2026.11.18). Last updated 19 November 2026, 10:09 GMT.
Critical by impact (our framing)
Oracle, the CVE CNA, and OpenJDK score this CVSS 3.1 8.1 High, with high attack complexity. Red Hat scores 9.8 Critical for its products. Atlassian scores 9.2 for its Data Center products. Security researchers, as reported by BleepingComputer: CVSS 4.0 9.2 Critical. We keep Critical by impact as our framing, because the official record describes takeover of the Java runtime and the press report describes unauthenticated code execution in default installs of widely used applications.
Compiler / Base64 decoder
The official advisories place the flaw in the hotspot/compiler (OpenJDK) or Compiler (Oracle) component. They describe an unauthenticated, network-reachable issue, with high attack complexity, that can result in takeover. Oracle Note 1 says it can only be exploited by supplying data to APIs in that component, for example through a web service, and not via untrusted Java Web Start applications or applets. BleepingComputer reports that security researchers describe memory corruption in the hardware-accelerated Base64 decoder, reachable only on x86-64 CPUs with AVX-512 VBMI, and only where an application feeds Base64 into that decoder. Red Hat says exploitation requires an x86-64 processor providing the avx512f, avx512bw, avx512vbmi and bmi2 features, that the vulnerable code path was introduced in OpenJDK 17.0.6, and that ARM64, OpenJDK 8 and OpenJDK 11 are not affected. We still record Oracle's listing of the 8u511b33-perf performance build as affected, which is a narrower Java 8 exception than Red Hat's general Java 8 statement.
Probing reported, not in KEV
SecurityWeek (19 November 2026, 09:10 GMT) reports internet-wide probing and blind exploit attempts, including requests with a java4shell-recon user-agent. In one case, a scanner probed, then returned about 17 hours later with the exploit trigger while posing as Chrome. Public reporting has not confirmed a successful compromise. The CVE was not in KEV when we rechecked on 19 November 2026 (catalogue 2026.11.18, released 19:17 GMT on 18 November 2026). SecurityWeek reports that the public proof of concept only triggers the memory corruption, and that security researchers report working remote code execution exploits exist privately. Cisco says it is aware of proof-of-concept code and has no knowledge of malicious use. We do not link proof-of-concept or exploit code. Recheck KEV.
17 November 2026 releases
The OpenJDK advisory says the vulnerabilities were fixed in the 17 November 2026 release, and lists 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 as the affected versions for that advisory. Oracle's Java SE matrix uses the heading "Supported Versions Affected" and lists the same 17, 21, 25 and 27 builds (plus 8u511b33-perf and the listed GraalVM builds). Those are the latest supported versions described as affected, not the fixed builds. The 17 November 2026 fixed builds, confirmed by the Oracle Java SE release notes, the OpenJDK JDK 27.0.1.1 release notes and Oracle's current JRE security baseline, are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Then take bundled-JRE updates from application vendors as they ship them.
| Item | Detail |
|---|---|
| CVE | CVE-2026-114938 (CNA: Oracle). Press and researchers also use the name Java4Shell. |
| Vendor score | Oracle (the CNA) and OpenJDK: CVSS 3.1 8.1 High. Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Red Hat: 9.8 Critical for its products. Atlassian: 9.2 for its Data Center products. Our page label remains Critical by impact (our framing). |
| Researcher score | CVSS 4.0 9.2 Critical, as reported by BleepingComputer. This is not an OpenJDK or Oracle score. |
| OpenJDK lines | The 17 November 2026 risk matrix marks 17, 21, 25 and 27 only. It does not mark 8 or 11 for this CVE, even though the advisory introduction lists 8u512 and 11.0.33 for the release as a whole. |
| Affected (OpenJDK, this CVE) | The advisory says: "The affected versions are 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." That sentence covers the whole 17 November 2026 advisory. The risk matrix for CVE-2026-114938 marks only the 17, 21, 25 and 27 lines, not 8 or 11. |
| Affected (Oracle, this CVE) | The Java SE risk matrix column is headed "Supported Versions Affected" and lists 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3 and GraalVM Enterprise Edition 21.3.20.0.3. Oracle's 17.0.21.0.3 release notes (24 October 2026) said not to use that build after the next critical patch update on 17 November 2026. The Java 8 entry is the 8u511b33-perf performance build only, not general Java 8, and Java 11 is not listed for this CVE. |
| Fixed builds (17 November 2026) | Confirmed by the Oracle Java SE release notes dated 17 November 2026, the OpenJDK JDK 27.0.1.1 release notes (release date 2026-11-17) and Oracle's current JRE security baseline: 17.0.21.1 (17.0.21.1+4), 21.0.13.1 (21.0.13.1+4), 25.0.5.1 (25.0.5.1+4) and 27.0.1.1 (27.0.1.1+4). For the listed Java 8 performance build, the matching 17 November 2026 release is 8u513-perf (1.8.0_513-perf-b4). Oracle GraalVM for JDK 21.0.13.1 is a confirmed 17 November 2026 CSPU release: its own release notes say it is built on Oracle JDK 21.0.13.1+4. Oracle GraalVM for JDK 17.0.21.1 and GraalVM Enterprise Edition 21.3.20.1 are under review, because their vendor notes conflict: both are labelled as the 17 November 2026 CSPU, but the notes say they are built on Oracle JDK 17.0.20.1+4, which is below the 17.0.21.1 fix. The Java 17-based Enterprise Edition build is the one given as 17.0.20.1+4; the same notes give 11.0.33.1+4 and 8u513-b04 for the Java 11 and Java 8 based builds. OpenJDK 8 and 11 are not marked for this CVE; 8u513 and 11.0.33.1 are the current security baseline for those families, but we do not list them as the fix for CVE-2026-114938. |
| Start of the 17 line | Red Hat says the vulnerable code path was introduced in OpenJDK 17.0.6, and that OpenJDK 8 and OpenJDK 11 do not contain it and are not affected. BleepingComputer also reports a start version of OpenJDK 17.0.6 and later, including downstream distributions. OpenJDK and Oracle do not themselves give a 17.0.6 start version. Oracle still lists the 8u511b33-perf performance build as affected, which we keep as a narrower Java 8 exception. |
| CPU and architecture (Red Hat) | Red Hat says exploitation requires an x86-64 processor providing avx512f, avx512bw, avx512vbmi and bmi2. ARM64 systems, and x86-64 processors without AVX-512 VBMI, are not affected. |
| NVD | Published 22:18 GMT on 17 November 2026. When we rechecked on 19 November 2026 the NVD status was Undergoing Analysis (last modified 21:17 GMT on 18 November 2026). The NVD copy still repeats Oracle's CVSS 3.1 8.1 score. NVD has not published its own CVSS assessment yet. CISA's SSVC record on that entry still lists Exploitation as "none" (timestamp 21:53 GMT on 17 November 2026), which predates the 19 November probing reports. |
| Activity reported (19 November 2026) | SecurityWeek at 09:10 GMT reports internet-wide probing and blind exploit attempts, including java4shell-recon user-agents and a later return posing as Chrome. Public reporting has not confirmed a successful compromise. Still absent from CISA KEV (catalogue 2026.11.18). |
| Red Hat rating | Red Hat rates this Critical, and says affected systems are vulnerable out of the box: the accelerated code path is selected automatically when the JVM runs on a CPU that reports AVX-512 VBMI support. No special configuration is required. Red Hat's CVSS v3 score is 9.8, which differs from the OpenJDK and Oracle score of 8.1. |
| Vendor product advisories | Cisco has confirmed 13 affected products, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance and Intersight Virtual Appliance, plus IOS XE and UCS Central still under investigation. Cisco rates the advisory High and says there are no fixes or workarounds yet. Elastic: Elasticsearch 7.17.3 and later (remote code execution needs read credentials; denial of service can be unauthenticated); Logstash 8.6.2 and later only in a specific configuration, crash or denial of service only. Elastic has announced fixes for upcoming releases 8.19.26, 9.4.10, 9.5.7 and 9.6.0; those fixes had not shipped when we checked. Atlassian Data Center: Jira, Jira Service Management, Confluence, Bitbucket, Bamboo and Crowd; workaround until patches: -XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions, published in an Atlassian Team forum post rather than a numbered advisory. Jenkins on Java 17, 21 or 25: update to the November Java release and restart. Keycloak container images 26.8.2-1 and 26.8.2-2 bundled a vulnerable OpenJDK 21 build; fixed in 26.8.2-3. Siemens: Industrial Edge Management Pro V1, Pro V2 and Virtual; Siemens says take them offline, or disable internet connectivity, until patched. |
What to Do in the Next 24 Hours
Vendor steps first, then our advice for internet-facing Java applications.
Inventory internet-facing Java first
Our advice: list every internet-facing Java application on x86 hosts, including Jira, Confluence, Jenkins, Keycloak, Elasticsearch, Cisco appliances, JFrog Artifactory and PingFederate, then other Java services. Record the distribution, the full version string, and whether the host CPU has AVX-512 VBMI (
grep avx512vbmi /proc/cpuinfoon Linux). Patch the runtime first.Upgrade the runtime
Vendor advice (OpenJDK and Oracle): upgrade as soon as possible to the 17 November 2026 OpenJDK release and the Oracle Java SE / GraalVM patches in the November 2026 CSPU. For the lines this CVE affects, the confirmed fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. For the Oracle Java SE 8u511b33-perf build listed as affected, use 8u513-perf. For GraalVM, Oracle GraalVM for JDK 21.0.13.1 is confirmed fixed. Treat Oracle GraalVM for JDK 17.0.21.1 and GraalVM Enterprise Edition 21.3.20.1 as under review, because their vendor notes conflict (they say they are built on Oracle JDK 17.0.20.1+4). Our advice: also apply bundled-JRE updates from the application vendors as they ship them, and do not assume a product installer is already on this runtime. Restart JVMs after you update.
If you cannot patch immediately
BleepingComputer reports that security researchers recommend a temporary workaround: start the JVM with
-XX:-UseBASE64Intrinsics, or with-XX:UseAVX=2to turn off AVX-512. We did not find those flags in the OpenJDK or Oracle advisories. Oracle's JDK 21javamanual says flags that control intrinsics, including-XX:+UseBASE64Intrinsics, now require-XX:+UnlockDiagnosticVMOptionsfirst. That option unlocks diagnostic JVM options, which the same manual says are disabled by default and are not supported. If you use the Base64 flag, put-XX:+UnlockDiagnosticVMOptionsbefore it, and treat the whole command line as a temporary measure. The same manual describes-XX:UseAVX=as enabling a specified AVX version, defaulting to the highest supported. Setting it to 2 limits the JVM to AVX2, so AVX-512 paths, including the Base64 decoder, are not used. That turns off all AVX-512 paths, not only the Base64 intrinsic, so the performance effect is wider than the Base64 flag alone. Product vendors have now published their own interim advice: Atlassian recommends disabling AVX-512 on Data Center products until patches ship; Jenkins, Keycloak and Elastic document-XX:-UseBASE64Intrinsics; Siemens recommends taking the affected Industrial Edge Management products offline, or disabling internet connectivity, until a fix is available; Cisco says there are no workarounds yet. Still plan the upgrade.Reduce exposure
Our advice: keep these applications behind SSO or a VPN, and off the public internet where you can, until the runtime is patched or the vendor workaround is in place. Put a VPN or WAF in front of anything you cannot patch today. Where a vendor has no fix yet, apply that vendor's workaround or take the system offline.
Look for signs of misuse
Our pattern, not vendor indicators: search web and proxy logs for
java4shell-reconuser-agents and unusual Base64-heavy requests, remembering that scanners now also pose as Chrome; unexpected JVM crashes or newhs_err_pid*.logfiles; unexpected child processes from Java, including shells or curl/wget spawned by Java service accounts; new outbound connections from application servers. Treat a crash followed by odd process activity as possible compromise: isolate, rotate the application's secrets, and rebuild from a known-good image.
Proactive: Vendor Steps, Then Ours
Vendor advice is labelled as such. Everything else is our advice.
Vendor advice
- OpenJDK and Oracle: upgrade as soon as possible to the 17 November 2026 release. For this CVE, the confirmed fixed builds in the marked lines are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. The builds listed as affected, including 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, should be replaced.
- Oracle: apply the November 2026 Critical Security Patch Update patches for Oracle Java SE and the listed GraalVM products, using the Patch Availability Documents linked from Oracle's advisory. Oracle GraalVM for JDK 21.0.13.1 is confirmed: its release notes say it is built on Oracle JDK 21.0.13.1+4. Treat Oracle GraalVM for JDK 17.0.21.1 and GraalVM Enterprise Edition 21.3.20.1 as under review, because their notes say they are built on Oracle JDK 17.0.20.1+4.
- Amazon Corretto: the 17 November 2026 changelogs name CVE-2026-114938 in Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4.
- Azul Zulu: the November 2026 release notes include CVE-2026-114938 in the risk matrix for lines 17, 21, 25 and 27, and list these November CSPU PSU builds: Zulu 17.70.201 (CA) and 17.70.202 (SA), based on JDK 17.0.21.1+2; 21.54.201 and 21.54.202, based on 21.0.13.1+2; 25.38.201 and 25.38.202, based on 25.0.5.1+2; and 27.30.201 and 27.30.202, based on 27.0.1.1+4.
- Red Hat: rates this Critical (CVSS 9.8 for its products) and says affected systems are vulnerable out of the box when the JVM runs on an x86-64 CPU that provides
avx512f,avx512bw,avx512vbmiandbmi2. The vulnerable path was introduced in OpenJDK 17.0.6; ARM64, OpenJDK 8 and OpenJDK 11 are not affected. Red Hat has published fixed builds of OpenJDK 17.0.21.1, 21.0.13.1 and 25.0.5.1 (advisories dated 18 November 2026). Some other Red Hat product packages were still listed as affected when we checked. - Microsoft Build of OpenJDK: the November 2026 critical patch update publishes fixed builds 17.0.21.1, 21.0.13.1 and 25.0.5.1.
- Eclipse Temurin: the 18 November 2026 Adoptium guidance lists fixed builds 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2 and 27.0.1.1+4. We confirmed those releases in the Adoptium API, with downloadable binaries for each line.
- Cisco: 13 products are affected, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance and Intersight Virtual Appliance. IOS XE and UCS Central are still under investigation. Cisco rates the advisory High, says there are no fixes and no workarounds yet, and says it is aware of proof-of-concept code and has no knowledge of malicious use.
- Elastic: Elasticsearch 7.17.3 and later are affected. Elastic says remote code execution needs valid credentials with read permissions or higher, and that a denial-of-service condition can be triggered without authentication. Logstash 8.6.2 and later are affected only in a specific configuration (the Elastic Integration filter, where an ingest pipeline decodes untrusted Base64), and Elastic says that path can cause a crash or denial of service, not code execution. Elastic has announced fixes for upcoming releases 8.19.26, 9.4.10, 9.5.7 and 9.6.0; those releases had not shipped when we checked. Elastic says it has already deployed a hotfix for Elastic Cloud Serverless and a configuration change for Elastic Cloud Hosted.
- Atlassian: Cloud customers do not need to take action. For Data Center products (Jira, Jira Service Management, Confluence, Bitbucket, Bamboo and Crowd), until patches are available, Atlassian recommends the workaround
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptionson the latest versions in standard installations, then restarting. That guidance is from an Atlassian Team forum post, not a numbered advisory. - Jenkins: controllers are at risk if they run a vulnerable Java 17, 21 or 25 release on a CPU with AVX-512 VBMI. Jenkins advises updating to the November Java releases (17.0.21.1, 21.0.13.1 or 25.0.5.1) and restarting. If you cannot upgrade immediately, Jenkins documents the temporary flag
-XX:-UseBASE64Intrinsics. - Keycloak: as checked on 18 November 2026, the 26.8.2-1 and 26.8.2-2 container images bundled a vulnerable OpenJDK 21 build. On 19 November 2026, Keycloak announced updated images containing a patched Java runtime, including 26.8.2-3 (and updated 26.8.2, 26.8 and latest tags) with Red Hat OpenJDK 21.0.13.1. Until you have deployed a fixed image or runtime, Keycloak documents
-XX:-UseBASE64Intrinsics. - Siemens: Industrial Edge Management Pro V1, Industrial Edge Management Pro V2 and Industrial Edge Management Virtual are affected. Siemens says no fix is available yet, and recommends shutting instances down or disabling internet connectivity until a fix can be applied.
- Restart JVMs after you apply a fixed runtime or a workaround flag.
- The official OpenJDK and Oracle advisories still do not publish a workaround flag, indicators of compromise, or a list of affected applications. Several product vendors have now published their own workarounds, as listed above.
Our advice
- Inventory internet-facing Java applications on x86 hosts first, including Jira, Confluence, Jenkins, Keycloak, Elasticsearch, Cisco appliances, Artifactory and PingFederate, then other Java services, including those that ship a bundled JRE.
- Check whether the host CPU exposes AVX-512 VBMI. BleepingComputer reports the hardware-accelerated decoder is only used on those x86-64 CPUs. Red Hat says the accelerated path is selected automatically on those CPUs, so affected systems are vulnerable out of the box. Absence of the flag lowers the likelihood, but do not use that as a reason to skip the upgrade.
- Patch the Java runtime first. Where a vendor has no fix yet, apply that vendor's workaround (Atlassian: disable AVX-512; the existing JVM flag workaround reported by BleepingComputer, and now also documented by Jenkins, Keycloak and Elastic) or take the system off the internet (Siemens' advice for the affected Industrial Edge Management products). Put a VPN or WAF in front of anything you cannot patch today.
- Apply application-vendor bundled-JRE updates as they ship, then restart the JVM. Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Eclipse Temurin and Red Hat have published fixed builds, as listed under Vendor advice. Do not assume a product installer already includes a fixed runtime.
BleepingComputer reports unauthenticated remote code execution, in default configurations, in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and authenticated remote code execution in Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. The same report says security researchers also triggered the flaw in sample applications built with Apache Struts and Spring Boot, and that there is no universal exploit: an attacker needs an application-specific way to feed Base64 to the decoder. Product names are from that report, not from OpenJDK or Oracle.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only. Pack version 1.1.0 is the current download on this page. It fixes the v1 IIS web-log hunt (Q6), which used a column that does not exist (sComputerName), and adds hunts for the java4shell-recon user-agent, the same IP returning within 48 hours posing as Chrome, and Base64-heavy parameters (low confidence), plus three new Sigma rules, a vendor workaround table, and checkers that report the CPU flags Red Hat lists. The earlier v1 pack folder remains in place, but readers should use v1.1.0. The KQL and Sigma have not been run against live data.
check-java4shell.sh
Read-only offline checker, pack version 1.1.0. The checker now reports the CPU flags Red Hat lists (avx512f, avx512bw, avx512vbmi and bmi2). Unpack the full pack first, so scripts/ stays in place. It opens no sockets, writes no files, never runs Java, and runs no other program except tr, head and wc. It reads a saved java -version output, a JDK release file or a Java home directory, plus optional CPU flags and JVM arguments. It never prints file content beyond version numbers, vendor names and the flags it checks. --show-args prints JVM arguments with secret values replaced by [REDACTED].
bash scripts/check-java4shell.sh --java-version-file java_version.txt --cpu-flags-file cpuinfo.txt --jvm-args-file cmdline.txtCheck-Java4Shell.ps1
The same checks in PowerShell 7, with identical output and exit codes. Run it from the unpacked full pack. It is also read-only, opens no sockets, writes no files and never runs Java.
pwsh -File scripts/Check-Java4Shell.ps1 -JavaVersionFile java_version.txt -CpuFlagsFile cpuinfo.txt -JvmArgsFile cmdline.txtKQL and Sigma
9 KQL hunts for Microsoft Sentinel and Defender, all OUR PATTERN, looking back from 17 November 2026 (our start date). Q1 to Q6 are the original hunts, with a fix in Q6: the v1 query used sComputerName, a column that does not exist in the IIS log table; v1.1.0 uses Computer. v1.1.0 adds three hunts: the java4shell-recon user-agent across web, proxy and WAF logs; the same IP returning within 48 hours posing as Chrome; and Base64-heavy parameters (low confidence). 9 Sigma rules, all OUR PATTERN, with Kusto conversions included, including three new rules in this version. OpenJDK and Oracle publish no indicators of compromise, so every hunt is OUR PATTERN, not a vendor IOC. The pack also includes a vendor workaround table citing each vendor's own page. The KQL and Sigma have not been run against live data. A hunt hit is a lead to investigate, not proof that code ran.
Verdicts
- NOT AFFECTEDThe Java version is a fixed build, or a release line OpenJDK and Oracle do not list for this CVE (exit 0).
- AFFECTEDThe version is affected and no workaround flag was seen, with AVX-512 VBMI present or unknown (exit 2).
- UNKNOWNNo usable version, a line the advisories do not cover, or a build the sources disagree on (REVIEW) (exit 3).
- MITIGATEDThe version is affected, but the JVM arguments carry an effective temporary workaround flag (exit 4).
- AFFECTED, CPU PRECONDITION ABSENTThe version is affected, no workaround was seen, and AVX-512 VBMI is absent on this CPU (exit 6).
Exit codes
| Code | Meaning |
|---|---|
| 0 | NOT AFFECTED |
| 1 | Not used |
| 2 | AFFECTED |
| 3 | UNKNOWN or REVIEW |
| 4 | MITIGATED |
| 5 | Usage or read error |
| 6 | AFFECTED, CPU precondition absent |
The full pack zip contains 74 files (pack version 1.1.0). The checker marks GraalVM for JDK 17.0.21.1 and GraalVM Enterprise Edition 21.3.20.1 as REVIEW, because the vendor notes conflict (see the versions section above).
Know the limits
- Both checkers are read-only and offline. They open no sockets, write no files, never run Java and contain no exploit payloads.
- OpenJDK and Oracle publish no indicators of compromise. Every hunt and Sigma rule in this pack is OUR PATTERN, not a vendor IOC.
- A hunt hit is a lead to investigate. It does not prove that code ran.
- The hunts look back from 17 November 2026. That start date is our choice.
- None of the KQL or Sigma has been run against live data.
What is in the pack
| File | What it does |
|---|---|
| scripts/check-java4shell.sh | Offline version, CPU-flag and JVM-argument checker for Linux and macOS (bash) |
| scripts/Check-Java4Shell.ps1 | The same checker in PowerShell 7 |
| KQL (9 hunts) | Microsoft Sentinel and Defender hunts Q1 to Q6, plus v1.1.0 hunts for the java4shell-recon user-agent, a later Chrome-posing return from the same IP, and Base64-heavy parameters (low confidence), all OUR PATTERN, from 17 November 2026 |
| Sigma (9 rules) | All OUR PATTERN, including three new rules in v1.1.0, plus Kusto conversions |
| tests/ | Fixtures, bash and Pester tests and a sandboxed no-network run |
| README.md | Verified facts, vendor vs our advice, checker usage, limits and sources |
Reactive: How to Hunt (Our Advice)
All of the following is OUR PATTERN, informed by the 19 November 2026 SecurityWeek report. OpenJDK and Oracle have published no indicators of compromise for this CVE. A hunt hit is a lead to investigate, not proof that code ran.
- Search web and proxy logs for the user-agent string
java4shell-recon, and for unusual Base64-heavy requests. SecurityWeek reports that scanners now also pose as Chrome, so do not rely on that user-agent string alone. - Unexpected JVM crashes, or new
hs_err_pid*.logfiles, on Java application servers. - Abnormally long Base64 strings in authentication headers, file-upload fields or API logs. We do not describe a crafted input pattern.
- Unexpected child processes from Java, including shells (
sh,bash,cmd, PowerShell) orcurl/wgetspawned by Java service accounts. - New outbound connections from application servers that do not normally make them.
Treat a crash followed by odd process activity as possible compromise: isolate the host, collect hs_err logs and relevant request logs, rotate the application's secrets, and rebuild from a known-good image. Patch the Java runtime (and the application's bundled JRE, if it has one) before returning the service to use.
Java4Shell CVE-2026-114938 FAQ
What is CVE-2026-114938, and why is it called Java4Shell?
CVE-2026-114938 is the official identifier. OpenJDK lists it under hotspot/compiler, and Oracle under the Compiler component of Oracle Java SE and GraalVM. The official CVE record describes a difficult-to-exploit, unauthenticated, network-reachable vulnerability that can result in takeover of the Java runtime, by supplying data to APIs in that component, for example through a web service. BleepingComputer reports that security researchers call it Java4Shell and describe it as memory corruption in the hardware-accelerated Base64 decoder. OpenJDK and Oracle do not use the Java4Shell name in their advisories.
How serious is it, and whose score should I use?
Use the scores labelled. Oracle, the CNA, and OpenJDK score it CVSS 3.1 8.1 High, with high attack complexity. Red Hat scores 9.8 Critical for its products. Atlassian scores 9.2 for its Data Center products. BleepingComputer reports that security researchers score it CVSS 4.0 9.2 Critical. We keep the page labelled Critical by impact (our framing) because of the official takeover wording and the reported effect on default installs of widely used applications.
Which versions are affected, and what is the fixed build?
The OpenJDK advisory says, of the 17 November 2026 release as a whole: "The affected versions are 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." Its risk matrix marks CVE-2026-114938 only on the 17, 21, 25 and 27 lines, not 8 or 11. Oracle's Java SE risk matrix, under the heading "Supported Versions Affected", lists 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3 and GraalVM Enterprise Edition 21.3.20.0.3. Those are the latest supported versions listed as affected, not the fixed builds. Oracle's own 17.0.21.0.3 release notes (24 October 2026) said not to use that build after the next critical patch update on 17 November 2026. The confirmed 17 November 2026 fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 (full version strings 17.0.21.1+4, 21.0.13.1+4, 25.0.5.1+4 and 27.0.1.1+4), plus 8u513-perf for the listed Java 8 performance build, and Oracle GraalVM for JDK 21.0.13.1. Oracle GraalVM for JDK 17.0.21.1 and GraalVM Enterprise Edition 21.3.20.1 are under review, because their vendor notes conflict (they say they are built on Oracle JDK 17.0.20.1+4, which is below the 17.0.21.1 fix). OpenJDK and Oracle agree that 17.0.21.0.3 and the matching 21, 25 and 27 builds are affected. BleepingComputer reports a start version of OpenJDK 17.0.6 and later; that start version is from the press report, not from the official advisories.
Has this been exploited, and is it in KEV?
Updated 19 November 2026. SecurityWeek (09:10 GMT) reports internet-wide probing and blind exploit attempts, including java4shell-recon user-agents, and a scanner that returned about 17 hours later with the exploit trigger while posing as Chrome. Public reporting has not confirmed a successful compromise. The CVE was not in CISA's Known Exploited Vulnerabilities catalogue when we rechecked on 19 November 2026 (catalogue 2026.11.18, released 19:17 GMT on 18 November 2026). CISA's ADP entry on the CVE record listed Exploitation as "none" when it was last updated at 22:02 GMT on 17 November 2026, which predates this reporting. We do not treat absence from KEV, or that earlier label, as proof that a flaw is unused. SecurityWeek reports that the public proof of concept only triggers the memory corruption, and that security researchers report working remote code execution exploits exist privately. Cisco says it is aware of proof-of-concept code and has no knowledge of malicious use. We do not link proof-of-concept or exploit code. Recheck KEV.
Is there a workaround if I cannot patch today?
The official OpenJDK and Oracle advisories still do not publish a workaround. BleepingComputer reports that security researchers recommend starting the JVM with -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 to turn off AVX-512, as a temporary measure. Oracle's JDK 21 java manual says intrinsic flags now require -XX:+UnlockDiagnosticVMOptions first, and that -XX:UseAVX=2 selects AVX version 2, which turns off all AVX-512 paths, not only the Base64 intrinsic. Product vendors have now also published interim advice: Atlassian recommends -XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions on Data Center products until patches ship (from an Atlassian Team forum post, not a numbered advisory); Jenkins, Keycloak and Elastic document -XX:-UseBASE64Intrinsics; Siemens recommends taking the affected Industrial Edge Management products offline, or disabling internet connectivity, until a fix is available; Cisco rates its advisory High and says there are no workarounds yet. Still plan the upgrade, apply application-vendor JRE updates as they ship, and restart the JVM.
What is the vendor's official advice?
Vendor advice from OpenJDK and Oracle: upgrade as soon as possible to the 17 November 2026 OpenJDK release, and apply the Oracle Java SE and GraalVM patches in the November 2026 CSPU. Until those patches are applied, those official advisories still do not offer a documented workaround. Product vendors have now published their own guidance: Cisco lists 13 affected products plus two under investigation, rates the advisory High, and has no fixes or workarounds yet; Atlassian recommends -XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions on Data Center products (from an Atlassian Team forum post, not a numbered advisory) and says Cloud customers do not need to take action; Jenkins says update to the November Java release and restart; Keycloak has patched images, including 26.8.2-3; Elastic has documented impact and mitigations for Elasticsearch and Logstash, and has announced fixes that had not shipped when we checked; Siemens recommends taking the affected Industrial Edge Management products offline until patched; Red Hat rates the issue Critical for its products (9.8) and has published fixed OpenJDK builds; Eclipse Temurin and Microsoft have also published fixed builds. Restart JVMs after you update.
Official Sources
- OpenJDK Vulnerability Advisory: 2026/11/17 (risk matrix marks this CVE on lines 17, 21, 25 and 27; last update 17:44 GMT on 17 November 2026).
- Oracle Critical Security Patch Update, November 2026 (Java SE and GraalVM risk matrix for CVE-2026-114938, including Note 1).
- CVE-2026-114938 at cve.org (CNA: Oracle; published 21:32 GMT on 17 November 2026).
- NVD record for CVE-2026-114938 (published 22:18 GMT on 17 November 2026; status Undergoing Analysis when we rechecked on 19 November 2026; last modified 21:17 GMT on 18 November 2026). CISA's SSVC record on that entry still lists Exploitation as "none" (17 November 2026, 21:53 GMT).
- CISA Known Exploited Vulnerabilities catalogue (catalogue 2026.11.18, released 19:17 GMT on 18 November 2026). This CVE was not in the catalogue when we rechecked on 19 November 2026.
- CISA alert: Critical Java Vulnerability Requires Immediate Patching (17 November 2026).
- Oracle GraalVM for JDK 17 release notes (17.0.21.1 entry dated 2026-11-17 says it is built on Oracle JDK 17.0.20.1+4).
- Oracle GraalVM for JDK 21 release notes (21.0.13.1 entry dated 2026-11-17 says it is built on Oracle JDK 21.0.13.1+4).
- Oracle GraalVM Enterprise Edition 21 release notes (21.3.20.1 entry dated 2026-11-17 gives 17.0.20.1+4 for the Java 17-based build).
- Amazon Corretto 17 changelog, and the matching 21, 25 and 27 changelogs (17 November 2026 builds that name CVE-2026-114938).
- Azul Zulu November 2026 Monthly Update Release Notes (risk matrix includes CVE-2026-114938; PSU builds listed above).
- Oracle JDK 21 java command manual (intrinsic flags and -XX:UseAVX=).
- Microsoft Build of OpenJDK, November 2026 critical patch update (fixed builds 17.0.21.1, 21.0.13.1 and 25.0.5.1).
- Eclipse Temurin guidance for CVE-2026-114938 (18 November 2026; fixed builds 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2 and 27.0.1.1+4, confirmed in the Adoptium API).
- BleepingComputer: Critical Java4Shell flaw allows RCE attacks on major Java applications (17 November 2026). Used for the Java4Shell name, the Base64 / AVX-512 VBMI description, the 17.0.6 start version and downstream distributions, the reported application impact, the CVSS 4.0 9.2 score, the temporary JVM flags, and the statement that a memory-corruption proof of concept is public. We do not link or reproduce that proof of concept.
- SecurityWeek: Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories (19 November 2026, 09:10 GMT). Used for the probing and blind exploit-attempt reporting, the
java4shell-reconuser-agent, the later return posing as Chrome, the public proof of concept triggering only memory corruption, the private remote code execution exploits reported by security researchers, and a round-up of vendor advisories that we then checked against each vendor's own page. We do not name or link the security firms or researchers cited in that article, and we do not link proof-of-concept or exploit code. - Cisco Security Advisory cisco-sa-nov2026-java-rce-eCa6ss9z (first published 16:00 GMT on 18 November 2026; last updated 21:16 GMT on 18 November 2026, version 1.1).
- Elastic: Java4Shell Remote Code Execution (RCE) Vulnerability, CVE-2026-114938 (18 November 2026).
- Atlassian: Data Center mitigations for CVE-2026-114938 (an Atlassian Team forum post, not a numbered advisory; workaround
-XX:UseAVX=2 -XX:+IgnoreUnrecognizedVMOptions). - Jenkins: Jenkins and Java4Shell (18 November 2026).
- Keycloak: Java4Shell, what Keycloak admins need to do (18 November 2026; last updated 19 November 2026, 08:00 UTC, confirming the 26.8.2-3 image).
- Siemens SSA-272816: Java4Shell Vulnerability in Industrial Edge (18 November 2026).
- Red Hat CVE-2026-114938 and the Red Hat security bulletin RHSB-2026-018 (Critical rating, 9.8 score, CPU flags, 17.0.6 start, ARM64 / Java 8 / Java 11 not affected, and fixed OpenJDK 17.0.21.1, 21.0.13.1 and 25.0.5.1 builds dated 18 November 2026).