Cyber Safety

Java4Shell Critical Memory Corruption Flaw Disclosed: What We Know

· GlobeWire Daily Editorial Desk · Source: www.techradar.com

2 min read

Key takeawaysSecurity researchers have disclosed a critical memory-corruption vulnerability in OpenJDK, tracked as CVE-2026-114938, which affects multiple Java distributions and enterprise applications. Oracle has released patches, and organizations are urged to update immediately or apply temporary mitigations.
JavaScript code on a computer screen

Image: TechRadar · Photo source · Resized and letterboxed to 16:9; no AI generation

Security researchers have disclosed a critical memory-corruption vulnerability in OpenJDK, tracked as CVE-2026-114938, which affects multiple Java distributions and enterprise applications. Oracle has released patches, and organizations are urged to update immediately or apply temporary mitigations.

Researcher Quang Long from Calif reported finding the vulnerability, dubbed Java4Shell, affecting OpenJDK's Base64 decoding functionality used on certain x86-64 processors supporting AVX-512 instructions. According to reported findings, the flaw could enable information disclosure or remote code execution.

Vulnerability Details and Severity

  • CVE Identifier: CVE-2026-114938
  • Severity Scores: Rated 8.1/10 (high) by the National Vulnerability Database (NVD) and 9.2/10 (critical) by Calif.
  • Affected Distributions: OpenJDK versions 17.0.6 and later, Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat OpenJDK.
  • Impacted Applications: Tested products include Jenkins, Atlassian Jira, Confluence, Keycloak, Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.

Mitigation and Verification

Oracle patched the vulnerability in its November Critical Security Patch Update released on November 17. Users and administrators should verify and install official updates promptly.

If immediate patching is not possible, temporary workarounds include:

  • Disabling hardware-accelerated Base64 functionality by launching OpenJDK with the `-XX:-UseBASE64Intrinsics` option.
  • Disabling AVX-512 instructions on x86-64 systems using `-XX:UseAVX=2`.

Organizations can verify their exposure by checking installed OpenJDK versions, auditing running enterprise applications, and reviewing official vendor advisories.

Share this article
Read the original source: Java hit by major security flaw — here's what we know about Java4Shell so far

AI-assisted reporting; source claims are attributed and have not been independently verified.

About the author

GlobeWire Daily Editorial Desk — AI-assisted news based on attributed published sources.

More to read