Ory’s Response to the Java4Shell (CVE-2026-114938) Vulnerability
Ory Network, Ory Enterprise License (OEL) and self-hosted Ory aren’t affected by Java4Shell, the OpenJDK Base64 heap overflow. This page tracks our status and sub-processor review.
Last updated: November 18, 2026
On November 17, 2026, Oracle and the OpenJDK project disclosed CVE-2026-114938, known as “Java4Shell.” It’s a heap overflow in OpenJDK’s Base64 decoder. It only affects x86-64 CPUs with AVX-512 VBMI support. On those machines, malformed Base64 input can crash the JVM, and in some applications it can lead to remote code execution. Affected builds include OpenJDK 17, 21, 25 and 27, plus downstream distributions such as Corretto, Temurin, Zulu and Red Hat OpenJDK. Patched builds are available now.
This page tracks Ory’s status. We’ll update it as our review continues.
Ory Network: Not affected. Ory Kratos, Hydra, Keto and Oathkeeper are written in Go, and Ory Polis is written in TypeScript/Node.js. No part of Ory Network runs on a Java Virtual Machine, and no Ory-operated system that handles customer data runs Java.
Ory Enterprise License (OEL) and self-hosted Ory: Not affected. Ory binaries and container images don’t include or depend on a JVM. No upgrade is needed to address this vulnerability.
Sub-processors: Review in progress. We’re contacting each sub-processor that handles customer data to confirm whether they’re exposed and, if so, when they’ll patch. We’ll update this page when the review is complete.
Indicators of compromise: We have found no indicators of compromise related to this vulnerability. If that changes, we’ll contact affected customers directly.
Your own environment: If you run Java services alongside Ory, such as an API gateway or a backend that calls Ory’s APIs, check them against your vendor’s advisory and upgrade to a patched JDK build (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, or your distribution’s equivalent).
Questions: Contact your Ory account team or [email protected].
Further reading

We're tracking several recently disclosed vulnerabilities, including the eMudhra certificate compromise and CVEs in PHP, Go, and Node.js. This page lists Ory's status for each one and will be updated as we learn more.

Most authentication proves someone holds the right credential, not which device they're holding it on. Device binding (also called device authentication) closes that gap: a private key generated in a phone's secure hardware, attested by Apple or Google, and used for step-up approval or full passwordless login via PIN or biometrics.

Introducing Ory Agent Security — authentication, authorization, and audit for the AI coding agents now working across your engineering org.

When AI agents generate millions of auth requests per second, traditional identity infrastructure breaks. Learn how Ory and CockroachDB solve agentic scale.

