Flaw in Java's foundation, Oracle releases fix
U.S. security firm Calif said on Nov. 17 (Nov. 18 Japan time) that it had found a critical vulnerability (an exploitable flaw) in "OpenJDK," the runtime that runs Java programs, and named it "Java4Shell." A Calif researcher found it using Codex. The flaw, tracked as CVE-2026-114938, sits in the part that handles Base64, a process that turns text data back into its original data. Oracle and OpenJDK released a fix and security advisories the same day.
OpenAI President Greg Brockman highlighted the flaw on X on Nov. 17 (7:29 a.m. Nov. 18 Japan time). His post names the company's cybersecurity model "GPT-6 Cyber" and its "Patch the Planet" initiative, and refers to the major flaw in Java that Calif found. Neither OpenAI nor Calif has said whether Calif used GPT-6 Cyber.
GPT-6 Cyber for helping further secure the internet, with a major security flaw in Java found by Calif, as part of our Patch the Planet initiative: https://t.co/DtMftfZTp7
Attackers could run programs remotely without authentication
According to Calif, feeding crafted Base64 data overwrites neighboring areas of memory. If exploited, attackers could read sensitive information from memory or run arbitrary programs remotely. Base64 is widely used in login authentication, file uploads and network messages.
Calif said it had demonstrated remote program execution in business software running default settings. Attacks worked before login in 6 products, including the development automation tool "Jenkins," Atlassian's "Jira" and "Confluence," and the authentication platform "Keycloak." After login, attacks worked in 5 products, including "Elasticsearch" and "Apache Kafka," it said. Calif said the list is not exhaustive.
The Cybersecurity and Infrastructure Security Agency (CISA), which protects U.S. critical infrastructure, urged organizations in a Nov. 17 alert to apply the fix immediately. It said crafted Base64 input could allow attackers to run programs remotely without authentication.
The severity score differs by version of the scoring system. Oracle gave the flaw 8.1 out of 10 on the common CVSS 3.1 scale and classified it as remotely exploitable without authentication. Calif rates it 9.2, "CRITICAL," under the newer CVSS 4.0.
Calif also said there is no attack that works as-is on every product, and each target requires tailored work. It said it will not publish the attack steps for individual products until updates have spread. As of Nov. 21, the materials reviewed did not say whether the flaw had been used in actual attacks.
Calif found it using Codex, within an hour
According to Calif's write-up, researcher Quang Luong told "Codex" to audit the JVM (the core of Java's runtime) and other areas. Codex found the flaw within an hour, and the first working attack code was ready 2 hours later. The total token cost of using the AI was less than $200, it said.
Calif's write-up names only Codex as the tool it used and mentions neither GPT-6 Cyber nor Patch the Planet. OpenAI unveiled GPT-6 Cyber on Nov. 5 (Nov. 6 Japan time) and began offering it to select approved customers. At the time, it named Calif as one of the companies using it. Oct. 24, the date Calif says it found the flaw, comes before that announcement. OpenAI and Calif have not disclosed which model was used in Codex or how this find relates to GPT-6 Cyber.
Patch the Planet is OpenAI's initiative to find and fix flaws in important software with AI, launched in June. Apart from Brockman's post, the relationship between this find and Patch the Planet has not been disclosed either. ORIENS could not retrieve the New York Times article Brockman shared in his post and has not checked its contents.
Impact limited to OpenJDK 17.0.6 and later, on some x86-64 CPUs
According to Calif, OpenJDK 17.0.6 and later are affected, including other companies' distributions built from OpenJDK. These include Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK and Oracle Java SE. OpenJDK's advisory says the flaw affects the 17, 21, 25 and 27 release lines.
The flaw sits in code that uses specific instructions for speed (AVX-512 VBMI), and occurs only on x86-64 CPUs that have them. Calif said affected CPUs include Intel Xeon chips such as Ice Lake and Sapphire Rapids, and AMD Zen 4 and later. ARM CPUs are not affected.
Oracle listed Java SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, among others, as affected versions. Calif said all Java users should update immediately. CISA advised organizations that cannot update right away to use temporary measures such as checking Base64 input, limiting its size and restricting unauthenticated access. Calif also described a way to avoid the flaw by turning off the speed-up code with a startup setting.
Reported publicly in June, fixed after Calif's report
Calif added an account of the history to its write-up on Nov. 19 (U.S. Pacific time). The same flaw had been reported by a user to the support desk of Adoptium, one of Java's distributors, on June 9, more than four months before Calif. In September, another developer pinned down the cause and proposed a fix to OpenJDK, but it was closed without being merged.
On Oct. 24, Calif reported the flaw, which it had found independently using Codex, to Oracle along with a demonstration that an attack works. It said it confirmed from the work logs that Codex had not looked at existing reports. Oracle lists Calif's researcher and one other person as reporters of this flaw.
Calif wrote that the flaw followed the same pattern as "PHP2Shell" in October, in that an already reported flaw was fixed after it was shown to be exploitable. PHP2Shell was also a flaw Calif found and reported, and Brockman had posted about it on X.
- A user reports the bug to Adoptium's support deskInvolved party
- Another developer proposes a fix to OpenJDK, later closedInvolved party
- Calif finds the flaw using Codex and reports it to OracleInvolved party
- Calif finds the June reportInvolved party
- Calif sends Oracle a demonstration of a pre-login attackInvolved party
- Calif asks Oracle to coordinate disclosureInvolved party
- Oracle releases fix, Calif publishes write-upOfficial
- Brockman highlights the flaw on XOfficial






