Live Updates

Critical Memory Corruption Vulnerability in OpenJDK Base64 Decoder (Java4Shell)

AI Analysis

CSSF has alerted supervised entities to CVE-2026-114938, a memory-corruption vulnerability in the OpenJDK Base64 decoder that can enable unauthenticated information disclosure, denial of service or remote code execution under exploitable conditions. Independent security commentary indicates that the risk is concentrated in internet-facing Java services receiving untrusted Base64 input on x86-64 systems with AVX-512 VBMI, while patched Java builds were released on 2026-11-17 and proof-of-concept exploit material is publicly available.

Key dates

2026-11-17
Oracle and OpenJDK security fixes for CVE-2026-114938 were reported as released in the November 2026 security updates.
2026-11-18
CSSF published its communiqué urging concerned supervised entities to review the CIRCL report and take appropriate action.

Suggested considerations

  • Firms should consider inventorying all Java runtimes, including bundled or embedded JDKs in third-party applications, and recording the vendor, full build version, operating system, processor architecture and whether AVX-512 VBMI is enabled.
  • Firms should consider prioritising internet-facing Java services that decode untrusted Base64 data, including authentication, API, JWT, SAML, file-upload and gateway functions, particularly on x86-64 hosts with AVX-512 VBMI support.
  • Firms should consider applying the relevant 2026-11-17 Oracle/OpenJDK security update or an equivalent vendor-fixed build and restarting affected Java processes. Reported fixed Oracle versions include Java SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, subject to confirmation with the relevant Java distributor.
  • Where immediate patching is not feasible, firms should consider documented compensating controls, such as disabling the affected Base64 intrinsics or AVX-512 functionality where supported, while assessing performance, availability and security trade-offs.
  • Security and compliance teams may wish to review web-server, application, authentication, endpoint and privileged-access logs for exploitation attempts, crashes, unusual memory-disclosure indicators or unexpected child processes, and preserve relevant evidence.
  • Firms should consider assessing whether exploitation, suspected exploitation or successful unauthorised access meets the definition of a major ICT-related incident under the applicable CSSF framework, rather than waiting for confirmed data loss or completed root-cause analysis.
  • DORA entities should consider preparing the initial notification within four hours of classifying the incident as major and no later than 24 hours after becoming aware of it, followed by the required intermediate and final reports. Non-DORA entities should consider applying the notification timelines and reporting stages in Circular CSSF 24/847.
  • Compliance teams may wish to document the vulnerability assessment, affected and unaffected assets, risk acceptance or compensating controls, patch evidence, incident-classification decision and any CSSF notification rationale.

What changed

The publication does not introduce a new standalone technical rule or patch deadline; it formally communicates CSSF's expectation that affected supervised entities review the CIRCL report and take appropriate remediation measures. CSSF expressly characterises successful unauthorised remote code execution as a major ICT-related incident requiring notification under Circular CSSF 25/893 for entities within DORA or Circular CSSF 24/847 for entities covered by the non-DORA framework. For DORA entities, Circular CSSF 25/893 applies the DORA incident-reporting process and the applicable RTS time limits: an initial notification as early as possible and within four hours of classification as major, and no later than 24 hours after awareness; an intermediate report within 72 hours of the initial no

Compliance impact

CSSF treats successful unauthenticated remote code execution arising from the vulnerability as an unauthorised malicious access and therefore as a major ICT-related incident for notification purposes under the applicable CSSF framework. The practical impact is potentially severe because independent analysis reports pre-authentication exploitation against widely used Java applications, although com

Who is affected

  • Luxembourg-authorised banks and other financial entities within the scope of DORA and supervised by CSSF
  • EU-authorised investment firms supervised by CSSF
  • Luxembourg investment fund managers and funds subject to Circular CSSF 24/847
  • Payment service providers and electronic money institutions subject to the relevant CSSF ICT-incident reporting framework
  • CSSF-supervised entities operating Java applications or relying on third-party applications containing vulnerable OpenJDK or Java SE runtimes
  • Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA)
  • Circular CSSF 25/893
  • Circular CSSF 24/847
  • Commission Delegated Regulation (EU) 2025/301 on major ICT-related incident reporting under DORA

AI-generated analysis. May contain errors or omissions — verify with the original CSSF source before acting. Full disclaimer.

What the CSSF said

CVE-2026-114938

Published by CSSF . Read the full notice at the source for the authoritative text.

Sectors

View Original on CSSF Back to Feed

Share this update