Skip to page content

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX news · Global

Critical Java4Shell Flaw in OpenJDK Enables Remote Code Execution on Major Enterprise Applications

Based on reporting from BleepingComputer

Published by the source: Tue, 17 Nov 2026 18:04:21 -0500

AEGLIX News

A severe flaw named Java4Shell has been found in OpenJDK that lets unauthenticated attackers run code remotely on common enterprise tools such as Jenkins, Atlassian Jira, Confluence, and Keycloak. The problem impacts OpenJDK 17.0.6 and newer releases, plus Java builds derived from the affected code base, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat OpenJDK.

Researchers from Calif achieved unauthenticated remote code execution against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, while also demonstrating authenticated RCE against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker. The vulnerability does not have a universal exploit, requiring attackers to find application-dependent methods to deliver malicious Base64 data to the vulnerable decoder.

Researcher Quang Luong uncovered the defect while auditing OpenJDK internals with OpenAI's Codex AI coding assistant, locating it in roughly one hour and crafting a first working exploit in about two more hours for a total AI cost under $200. Calif has published a proof-of-concept that shows the memory corruption but has not made public the weaponized exploits used against the listed enterprise applications.

Oracle issued fixes for CVE-2026-114938 on November 17 as part of its November Critical Security Patch Update, which covers 655 security vulnerabilities across its product line. Calif advises turning off the vulnerable hardware-accelerated Base64 feature by starting OpenJDK with the -XX:-UseBASE64Intrinsics flag, or using -XX:UseAVX=2 to disable AVX-512 instructions on x86-64 systems as interim workarounds.

Report prepared 2026-11-17 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.

Sources

Read original source · BleepingComputer (opens in a new tab)

Privacy policy

Explore the story

Consult the cited publisher for the original reporting, updates and supporting evidence. Check the publication date and source before acting on a headline.

These are research tools; no CVE, indicator, or campaign relationship is inferred from this article.

More from BleepingComputer

← Back to security news