공지 > 텍스트

Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)

2026-11-19 10:33:55

Dear Customers,

A memory corruption vulnerability in the OpenJDK Base64 decoder (CVE-2026-114938, known as “Java4Shell”, Severity: High, Disclosed: November 17, 2026) has been publicly disclosed.

The issue stems from an output length calculation flaw during AVX-512 hardware-accelerated Base64 decoding on certain x86-64 CPUs. Crafted Base64 inputs can trigger a heap out-of-bounds write and, under specific conditions, lead to service disruption/process crash, sensitive data exposure, or Remote Code Execution (RCE).

Vulnerability Details

  • Prerequisites (All Generally Required): Affected OpenJDK/JDK version + x86-64 CPU supporting AVX-512 VBMI + attacker-controlled data reaching Java Base64 decoding (e.g., HTTP Basic auth, SAML, tokens, file uploads) + affected hardware acceleration not disabled. ARM64 and CPUs without AVX-512 VBMI are outside the known affected scope.
  • Impacted Scope: Resides in the Java runtime layer, potentially affecting Java applications and middleware such as Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory, and PingFederate.
  • Affected Versions: OpenJDK 17.0.6+ with the affected implementation, plus specific builds of Oracle Java SE (e.g., 88u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3) and Oracle GraalVM (e.g., 17.0.21.0.3, 21.0.13.0.3, 21.3.20.0.3). For other distributions (Corretto, Temurin, Microsoft Build, Zulu, Liberica, Red Hat, SapMachine) and branches like OpenJDK 8 or 11, check vendor advisories.
  • Patched Versions: Oracle Java SE fixed builds 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, and later; follow respective vendor patches for other distributions.

CDNetworks Protection Measures

Measure Details
WAF Rule Rule ID: 9660, detecting and blocking malicious requests targeting CVE-2026-114938
Coverage Domains onboarded to Cloud Security 2.0 / Flood Shield 2.0 with Rule 9660 enabled in protection/blocking mode
Monitoring Continuous tracking of patches and exploitation activity, with rule updates as needed

Recommended Actions

Please take action based on your onboarding status:

  • Onboarded, WAF in Protection/Blocking Mode: Confirm Rule 9660 is enabled and enforced.
  • Onboarded, WAF Disabled or Monitor-Only: Contact technical support promptly to evaluate switching to protection/blocking mode and enabling Rule 9660.

Component Remediation Steps

While the WAF blocks attacks when malformed Base64 payloads are sent in HTTP traffic through CDNetworks, it cannot cover every path reaching the vulnerable decoder. Therefore, we recommend applying server-side updates as soon as possible by following the steps below:

  1. Asset Inventory: Check JDK distributions and exact build versions, whether host CPUs support AVX-512 VBMI, and external endpoints processing Base64 inputs.
  2. Patch Application: Prioritize internet-facing Java apps, identity services, and critical middleware, upgrading to patched builds (such as Oracle 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, or later).
  3. Temporary Workaround: If upgrades are delayed, evaluate JVM flags to disable hardware acceleration (prefer -XX:-UseBASE64Intrinsics; -XX:UseAVX=2 is for x86-64 only, never ARM64), and remove temporary flags once patched.
  4. Restart & Verify: Restart affected applications, middleware, or containers after changes, and verify running process versions and active flags.

CDNetworks will continue monitoring threat activity to assist customers in maintaining a robust security posture. For technical assistance, please contact your account manager or support team.

Sincerely,
CDNetworks Security Team
November 2026