• /
  • EnglishEspañolFrançais日本語한국어Português
  • Inicia sesiónComenzar ahora

NR26-16: OpenJDK (Java4Shell) Remote Code Execution Flaw (CVE-2026-114938)

|View as Markdown (English)

Vulnerability Identifier: NR26-16

Priority: Critical

Summary

A critical memory corruption vulnerability (CVE-2026-114938) has been disclosed in the hardware-accelerated Base64 decoder of the OpenJDK HotSpot Java Virtual Machine (JVM). When an affected Java application processes specially crafted Base64-encoded input (such as HTTP Authorization headers, JWTs, SAML tokens, or file uploads), an integer underflow can trigger an out-of-bounds heap write. Successful exploitation can cause application crashes (Denial of Service), expose sensitive heap memory, or allow unauthenticated Remote Code Execution (RCE).

Action items

No action required

New Relic does not ship a Java runtime with the New Relic Java agent. No customer action is required for New Relic-hosted services, including Synthetics public locations.

Customer action is required in the following cases.

Synthetics private locations (Synthetics Job Manager and ping runtime)

The Synthetics Job Manager (SJM) and the ping runtime for private locations include a Java runtime. Updated images containing a patched Java runtime were published on November 19, 2026.

Your Java applications, including those monitored by the New Relic Java agent

Your Java applications are affected only when all of the following are true:

  • The application runs on a HotSpot-based OpenJDK distribution, version 17.0.6 or later (but prior to the November 2026 critical patch update). Examples include Oracle Java SE, Amazon Corretto, Eclipse Temurin, Azul Zulu, Red Hat OpenJDK, and Microsoft Build of OpenJDK.
  • The host has an x86-64 processor with AVX-512 VBMI support (Intel Xeon Ice Lake or newer, or AMD Zen 4 or newer). ARM64 processors, including AWS Graviton, aren't affected.
  • The application processes untrusted input that can reach Java's Base64 decoder.

Fix: Update your Java runtime to your vendor's November 2026 security release, starting with internet-facing systems. For details, see Oracle's Critical Security Patch Update (November 2026), the OpenJDK Vulnerability Advisory (2026/11/17), or your JDK vendor's advisory.

Frequently asked questions

  1. Does this affect New Relic's agents?

    The New Relic Java agent doesn't bundle or distribute a Java runtime (JDK/JVM). It instruments Java applications using the Java runtime available in the application's environment.

  2. Do I need to update the New Relic Java agent?

    No. The New Relic Java agent doesn't include a Java runtime, and no Java agent update is required for this vulnerability.

  3. Which systems are affected?

    Only x86-64 processors that support AVX-512 VBMI. ARM64 processors aren't affected. OpenJDK and Oracle have published fixes.

  4. How do I know whether my Java runtimes for my applications are affected?

    Check the Java version and the CPU. For applications monitored by New Relic APM, the JVM version is shown on the service's Environment page. See Get environment data about your APM app for more details, and be sure to select your hosts. Alternatively, on a host, run java -version.

    On Linux, check the CPU with:

    bash
    $
    grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

    The CPU is affected only if all four flags appear.

  5. How do I fix the vulnerability?

    Update your Java runtime to your vendor's November 2026 security release, starting with internet-facing systems. For details, see Oracle's Critical Security Patch Update (November 2026), the OpenJDK Vulnerability Advisory (2026/11/17), or your JDK vendor's advisory.

  6. What can I do if I can't patch right away?

    Start the JVM with JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics" as a temporary mitigation. On x86-64 hosts only, you can use -XX:UseAVX=2 instead. JVMs on ARM don't recognize this option and will fail to start. Both options are temporary and don't replace patching.

  7. Has New Relic seen evidence of exploitation?

    We haven't identified indicators of exploitation of this vulnerability in our environment.

  8. What if I have questions?

    For any support needs related to this communication, open a support case through in-app support.

Technical vulnerability information

Publication history

November 17, 2026 - OpenJDK vulnerability advisory published

November 20, 2026 - NR26-16 Published

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.