Urgent advisory: Critical OpenJDK & Oracle Java Remote Code Execution vulnerability ("Java4Shell" – CVE-2026-114938) impacting enterprise environments

 

1 | Incident summary

RSM Hong Kong is tracking security advisories and public proof-of-concept (PoC) exploits for CVE-2026-114938 ("Java4Shell"). This is a heap-based buffer overflow (out-of-bounds write) in the AVX-512-optimised Base64 decoding routine of the x86-64 HotSpot JVM.


Oracle fixed the flaw in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026. The update covers 11 Java SE flaws. Oracle and the NVD rate this CVE CVSS 3.1 8.1 (High). 


The flaw sits in OpenJDK code, so it also affects Oracle Java SE, Oracle GraalVM and downstream distributions. These include Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.


An unauthenticated remote attacker can send crafted Base64-encoded input to a vulnerable application. Examples are HTTP Basic authentication headers, JWTs, SAML payloads and cookies. This can cause memory corruption, sensitive memory disclosure ("JavaBleed") and, in some applications, remote code execution (RCE). Public PoCs have targeted applications such as Jenkins, Jira, Confluence and Keycloak. Impact depends on the application. For example, Elastic reports that Elasticsearch RCE requires an authenticated user.

 

 

2 | Risk exposure and business impact

      

Server and container takeover 
Internet-facing Java services that process attacker-controlled Base64 input may be exposed to RCE without authentication.

Credential and data exposure
Memory disclosure may leak API keys, session tokens, database credentials and confidential records from JVM memory.

Operational disruption 
Public PoCs accelerate automated scanning. Emergency runtime upgrades across many microservices and vendor appliances can strain IT and DevOps teams.

3 | Immediate recommended actions

RSM recommends taking these steps immediately:

Interim mitigation, if patching is delayed

  • Disable the vulnerable AVX-512 path by starting the JVM with -XX:UseAVX=2. You can instead disable the Base64 intrinsic with -XX:-UseBASE64Intrinsics. Restart the service after either change.
  • Place internet-facing Java portals, API gateways and identity providers behind a WAF, and restrict unnecessary public exposure. A WAF is not a complete fix, because the malformed input can arrive in many headers and payloads.

     

Remediation

  • Inventory Java runtimes across production servers, containers, CI/CD pipelines and third-party appliances. Include OpenJDK, Oracle Java SE and GraalVM, and the 17, 21, 25 and 27 release lines. Also check Oracle Java SE 8 (8u511b33-perf is listed as affected) against Oracle's advisory.
  • Upgrade to patched builds: 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, or the equivalent vendor releases. Check each vendor's advisory for exact build numbers.
  • Restart all JVMs and containers so running processes load the patched runtime.
  • Review the Oracle CSPU and GovCERT.HK alert A26-11-35 for the full list of fixed flaws.

     

 

How RSM Hong Kong can assist

RSM Hong Kong's Technology and Management Consulting (TMC) team can help with:

Vulnerability scanning and
asset discovery 
We identify internet-exposed Java services, APIs and vulnerable runtime versions across on-premises and cloud environments.

IT health checks and
patch governance 
 We review JVM configurations, verify interim mitigations, and support structured runtime upgrades across microservices.

Cyber resilience and
incident readiness review 
We assess network segmentation, WAF rulesets and detection capabilities against pre-authentication memory-corruption and RCE threats.