# CVE-2026-114938 (Java4Shell): Memory corruption in Oracle GraalVM Enterprise Edition

> Unauthenticated remote attackers supplying data to Java SE Compiler APIs can trigger a heap overflow and take over the JVM; Java and GraalVM users should patch.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes
- **Fix available:** Yes
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** ALPINE-CVE-2026-114938, BELL-CVE-2026-114938, CLEANSTART-2026-WU06013, DEBIAN-CVE-2026-114938, DHI-gdkb-bg4u-ky3w-y23l, ECHO-8328-846a-7af0, GHSA-6g7j-4xh3-xq2q, UBUNTU-CVE-2026-114938

## What is CVE-2026-114938?

CVE-2026-114938 (Java4Shell) is a high-severity memory corruption vulnerability in Oracle GraalVM, published on 17 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler).  Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK: 17.0.21.0.3 and  21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition.  Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-114938?

It affects 20 products.

An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.


Products: AWS Corretto, Cg-skills, Oracle GraalVM, Oracle GraalVM for JDK, Oracle Java SE JDK and JRE, Oracle Java SE JDK and JRE, Red Hat Amq Broker, Red Hat build of Apicurio Registry, Red Hat Build Of Cryostat, Red Hat build of Keycloak, Red Hat Build Of Openjdk, Red Hat build of Quarkus, Red Hat Data Grid, Red Hat Enterprise Linux, Red Hat Hardened Images, Red Hat JBoss Enterprise Application Platform, Red Hat Jboss Web Server, Red Hat Openshift Pipelines, Red Hat Streams For Apache Kafka, Siemens Industrial Edge Management Pro.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:amazon:corretto:*:*:*:*:*:*:*:*` from 27.0.0.33.1 up to 27.0.1.1.4
- `cpe:2.3:a:chainguard:cg-skills:-:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:graalvm:21.3.20.0.3:*:*:*:enterprise:*:*:*`
- `cpe:2.3:a:oracle:graalvm_for_jdk:17.0.21.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:graalvm_for_jdk:21.0.13.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jdk:1.8.0:update511_b33:*:*:enterprise_performance_pack:*:*:*`
- `cpe:2.3:a:oracle:jdk:17.0.21.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jdk:21.0.13.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jdk:25.0.5.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jdk:27.0.1.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jre:1.8.0:update511_b33:*:*:enterprise_performance_pack:*:*:*`
- `cpe:2.3:a:oracle:jre:17.0.21.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jre:21.0.13.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jre:25.0.5.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:oracle:jre:27.0.1.0.3:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:amq_broker:7.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:build_of_apicurio_registry:3.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:build_of_cryostat:4.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:build_of_openjdk:*:*:*:*:*:*:*:*` from 17.0.0 before 17.0.21.1
- `cpe:2.3:a:redhat:build_of_openjdk:*:*:*:*:*:*:*:*` from 21.0.0 before 21.0.13.1
- `cpe:2.3:a:redhat:build_of_openjdk:*:*:*:*:*:*:*:*` from 25.0.0 before 25.0.5.1
- `cpe:2.3:a:redhat:build_of_quarkus:-:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:data_grid:8.0:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:enterprise_linux:10.0:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:hardened_images:-:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:jboss_enterprise_application_platform:7.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:jboss_enterprise_application_platform:8.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:jboss_web_server:7.0.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:openshift_pipelines:-:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:streams_for_apache_kafka:3.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:siemens:industrial_edge_management_pro:*:*:*:*:*:*:*:*` from 1.0.0 up to 2.2.1

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `redhat:build_of_openjdk`, `amazon:corretto`, `siemens:industrial_edge_management_pro` | 17.0.21.1, 21.0.13.1, 25.0.5.1 |

## How do I fix CVE-2026-114938?

Apply the vendor's patch.

## Is CVE-2026-114938 being exploited?

There is no known exploitation of CVE-2026-114938 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-114938 — OpenJDK AVX-512 Base64 heap overflow PoC, scanner & detection rules (Suricata, Sigma, ModSecurity). Memory corruption in HotSpot's VBMI intrinsic. (github_poc): https://github.com/ikow/java4shell-poc
- curl -fsSL https://files.xint.io/java4shell | sh (github_poc): https://github.com/theori-io/java4shell-runtime-patch-CVE-2026-114938
- Java4Shell CVE-2026-114938 Analysis and Lab (github_poc): https://github.com/Dungsocool/CVE-2026-114938
- OpenJDK / Java exploits - CVE-2026-114938 Java4Shell and more (github_poc): https://github.com/Ghost-Bx1/java-exploits
- CVE-2026-114938 Java4Shell (CVSS 9.2) Base64 heap overflow Red/Blue toolkit. JDK/CPU exposure checks, bounded local proof, crash and mitigation tests, remote version scan, --profile heap hints, --persist/--exfil helpers, SOCKS5/Tor, stealth jitter, JSON reports. Experimental probe; experimental RCE chain. Only authorized security testing. (github_poc): https://github.com/tc4dy/CVE-2026-114938-Toolkit
- CVE-2026-114938 (github_poc): https://github.com/ashrafzaryouh/CVE-2026-114938

## Other vulnerabilities in Oracle GraalVM

- [CVE-2025-50059](https://insights.sbomify.com/CVE-2025-50059/): Security feature bypass in Oracle GraalVM Enterprise Edition (high 8.6)
- [CVE-2025-30749](https://insights.sbomify.com/CVE-2025-30749/): Other in Oracle GraalVM Enterprise Edition (high 8.1)
- [CVE-2025-50106](https://insights.sbomify.com/CVE-2025-50106/): Other in Oracle GraalVM Enterprise Edition (high 8.1)
- [CVE-2026-62574](https://insights.sbomify.com/CVE-2026-62574/): Privilege escalation in Oracle GraalVM Enterprise Edition (high 7.8)
- [CVE-2020-2802](https://insights.sbomify.com/CVE-2020-2802/): Denial of service in GraalVM Enterprise Edition (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114938 (Java4Shell) and fix it if it is affected.

What it is: CVE-2026-114938 (Java4Shell) is a high-severity memory corruption vulnerability in Oracle GraalVM, published on 17 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-114938 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.

Affected product: Oracle GraalVM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114938/ (Markdown: https://insights.sbomify.com/CVE-2026-114938/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114938
- OSV: https://osv.dev/vulnerability/CVE-2026-114938

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114938/
Summaries are generated and may contain mistakes; the official description above is the record.
