Bug 2574227 (CVE-2026-114938) - CVE-2026-114938 OpenJDK: OpenJDK: remote code execution via memory corruption on x86-64 systems with AVX-512 VBMI
Summary: CVE-2026-114938 OpenJDK: OpenJDK: remote code execution via memory corruption...
Keywords:
Status: NEW
Alias: CVE-2026-114938
Deadline: 2026-11-17
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-17 06:03 UTC by OSIDB Bzimport
Modified: 2026-11-18 00:10 UTC (History)
72 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-17 06:03:37 UTC
Calif reports a memory-corruption vulnerability in OpenJDK, named Java4Shell. On affected JVMs, malformed input may lead to remote code execution. The reported affected scope is OpenJDK Java 17.0.6 and later on x86-64 CPUs where AVX-512 VBMI is available. Native ARM64 JVMs are reported unaffected. The exact affected release lines and fixed build numbers require confirmation when Oracle publishes its update.

Initial testing reportedly demonstrated pre-auth remote code execution in default configurations of Apache Kafka Broker, Atlassian Confluence, Atlassian Jira, JFrog Artifactory, Gerrit, Jenkins, Keycloak, and PingFederate. Elasticsearch was reported post-auth; Spring Boot exposure is application-specific.

Potentially relevant CPUs include Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, and Granite Rapids; AMD EPYC Zen 4–6; and AMD Ryzen Zen 4–5. The notice identifies AWS C6i/M6i/R6i, C7i/M7i/R7i, C7a/M7a/R7a; Google Cloud C3/C3D, C4/C4D, N4/N4D, M3/M4; and Azure Intel D-series v5/v6/v7 and AMD D-series v6/v7 as screening examples. Confirm the CPU feature and the actual JVM used for each deployment.

Interim mitigation supplied by the reporter: start affected x86-64 JVMs with -XX:UseAVX=2. Do not apply this flag to ARM JVMs. Prepare runtime updates, container rebuilds, redeployments, and application restarts. For bundled runtimes, follow the product vendor’s supported update path.


Note You need to log in before you can comment on or make changes to this bug.