An optimized decoder can write past its buffer

CVE-2026-114938 is a memory-corruption flaw in an optimized Base64 decoder used by affected OpenJDK and Oracle Java builds. CERT-EU says specially crafted input can crash a JVM and, under some conditions, lead to unauthenticated remote code execution. Calif, the researcher that disclosed the issue, reports working application-specific code-execution chains in lab testing, including paths through Keycloak, Jira and Jenkins. That research does not establish that those applications are being exploited in the wild.

This is not a vulnerability in every Java process. CERT-EU lists three conditions that must line up: an x86-64 processor exposing the required AVX-512 features, the relevant decoder intrinsic running, and attacker-controlled Base64 reaching it. Affected software can also carry its own Java runtime, so a host-level package inventory is only a starting point.

A product name is not an exposure verdict

Calif says there is no universal exploit. Each demonstrated chain depends on the application and its input path. Treat a vulnerable Java version as a reason to investigate and patch, not proof that a specific service is remotely exploitable.

Check what is actually running

  1. 1

    Find Java in applications and containers. Inventory JDKs and runtimes installed on hosts, bundled in applications and baked into container images. Record the vendor, release, running process and owner of each service.

  2. 2

    Test the prerequisites. Check whether the host or virtual machine exposes the relevant AVX-512 features and whether the running JVM uses the Base64 intrinsic. Prioritize internet-facing services that decode untrusted authentication or application data.

  3. 3

    Apply the right vendor build. Use the Java distributor's fixed release or the application vendor's patched bundle. Restart the JVM and verify the active runtime; replacing a file on disk does not update an already running process.

A temporary switch buys time, with a restart

CERT-EU describes a temporary JVM option to disable the affected Base64 intrinsic when a fixed build is not yet available. That option needs a service restart and should be tested against application performance. It is a bridge to a vendor update, especially where Java is embedded in a product that follows its own release schedule.