# CVE-2026-114939: Other in Oracle GraalVM Enterprise Edition

> Unauthenticated remote attackers can compromise Java SE and GraalVM JGSS to read and modify data, mainly affecting sandboxed untrusted Java deployments.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **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:** No
- **Fix available:** Yes
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** ALPINE-CVE-2026-114939, BELL-CVE-2026-114939, DEBIAN-CVE-2026-114939, DHI-6gna-owgh-htn4-suec, ECHO-cdc2-f79a-3cba, GHSA-4m4x-94xr-j9xp, UBUNTU-CVE-2026-114939

## What is CVE-2026-114939?

CVE-2026-114939 is a high-severity other vulnerability in Oracle GraalVM Enterprise Edition, 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: JGSS).  Supported versions that are affected are Oracle Java SE: 8u511b33, 8u511b33-perf, 11.0.33.0.3, 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  unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as  unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 7.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

Weakness: CWE-284 (Improper Access Control)

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

An affected version is exposed as installed. No special setting or call is needed.


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

Apply the vendor's patch.

## Is CVE-2026-114939 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114939 and fix it if it is affected.

What it is: CVE-2026-114939 is a high-severity other vulnerability in Oracle GraalVM Enterprise Edition, 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-114939 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Oracle GraalVM Enterprise Edition. 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-114939/ (Markdown: https://insights.sbomify.com/CVE-2026-114939/index.md)
```

## Sources

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

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