Skip to content

+Threat Wire · Reference

Java4Shell: remote code execution in OpenJDK

A reported out-of-bounds write in OpenJDK, tracked as Java4Shell, could let an unauthenticated attacker run code in Java applications.

Prioritize patchingCVE-2026-114938Checked Nov 17

What it means for your AI agents

Agent backends, MCP servers and webhook receivers are usually built on these runtimes and libraries. A flaw that runs code before authentication hands an attacker the agent's keys and tool access, not just the server.

  • Check the services behind your agents and MCP tools, including ones that only call outward.
  • Look for the affected component in dependencies too, not just the runtime you installed directly.
  • Until patched, treat output from an affected service as untrusted input to your agents.

Updates

  • Nov 17, 2026 : Oracle released patched Java SE builds in its November update, and Calif disclosed Java4Shell (CVE-2026-114938).

Details

Calif discovered and reported CVE-2026-114938, which it calls Java4Shell. Datadog Security Labs describes it as an out-of-bounds write in OpenJDK, a flaw in the Java runtime itself rather than in a third-party library. According to Datadog, the bug is reached before an application can reject the input, so the application's own validation does not protect it.

Early reports name OpenJDK 17.0.6 and later as affected and rate the flaw 9.2 under CVSS 4.0. Oracle scores Java flaws under CVSS 3.1, and its highest Java SE score in the November update is 8.1; Aikido notes that the two figures may describe different issues.

As of November 17, the vulnerable component and the conditions for exploitation are not public, and the CVE record has not been published. Calif has said it will publish technical details after Oracle's patch release.

Risk

An unauthenticated attacker may be able to run code in a Java application before it can reject the input. Aikido had seen no reports of exploitation as of November 17.

Affected deployments

Oracle lists Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, GraalVM for JDK 17.0.21 and 21.0.13, and GraalVM Enterprise Edition 21.3.20.0.3 as affected by its November update. OpenJDK builds from other vendors, distribution packages, and JDKs bundled in applications or container images can be affected too.

Evidence and sources5 links

CVE record

As of November 17, the CVE record is not published, so the CVSS 4.0 score of 9.2 comes from early reports, not from the record.

CVE-2026-114938

Vendor advisory

Oracle lists the affected Java versions in its November update.

Oracle Critical Security Patch Update, November 2026

Java SE 17.0.21.1 release notes

Security research

Datadog describes the out-of-bounds write. Aikido lists the patched build for each Java line and notes the CVSS mismatch.

Datadog Security Labs

Aikido

Check your exposure with an agent

Paste this into an AI agent that can see your infrastructure. It asks for a read-only check of what's affected, including the systems behind your agents, and a table you can act on. Copying it changes nothing.

Prompt
Assess whether the infrastructure you can access is affected by Java4Shell: remote code execution in OpenJDK (CVE-2026-114938). Work read-only within your authorized access: do not run exploits, change configuration, restart services or install anything.

1. Confirm the affected and fixed versions from the vendor advisories and CVE records:
   - https://www.oracle.com/java/technologies/javase/17-0-21-1-relnotes.html
   - https://www.cve.org/CVERecord?id=CVE-2026-114938
   - https://www.oracle.com/security-alerts/cspunov2026.html
   - https://securitylabs.datadoghq.com/articles/java4shell-remote-code-execution-in-openjdk-cve-2026-114938
   - https://www.aikido.dev/blog/java-17-rce-vulnerability-cve-2026-114938
   Cite each source and the date you read it. Say plainly what you could not verify.

2. Inventory the systems that could run the affected software, including the hosts, containers, MCP servers, tool runners and sandboxes behind any AI agents. For each, record the asset, environment, owner if known and the version actually running, from read-only evidence (package metadata, version commands, platform inventory).

3. Note which affected systems are reachable from the internet or from agents and tools, and which credentials (model-provider keys, tool tokens, service accounts) are stored on them.

4. Report one row per asset: asset, running version, affected (yes / no / unknown), reachable from, credentials at risk, evidence, and the next step. List anything you could not access as a gap rather than assuming it is safe.

More from the Threat Wire

Briefing source: Cloudflare Radar Zero Wire (Cloudforce One), last checked November 17, 2026. Refreshed here every 30 minutes.