A critical security vulnerability in OpenJDK was discovered by a researcher in just one hour using AI, with the total token cost coming in at less than $200. The finding underscores how AI is collapsing the cost and time required to uncover high-impact flaws in foundational enterprise software.
Security company Calif disclosed Java4Shell (CVE-2026-114938), a memory-corruption vulnerability in OpenJDK’s Base64 decoder. OpenJDK is the most popular Java runtime, and under version 4.0 of the Common Vulnerability Scoring System, this vulnerability scores 9.2 out of 10.
As the world's third most popular programming language, Java powers 90% of Fortune 500 companies and spans banking, aviation, telecommunications and national security systems.
While Java is designed to prevent memory corruption, its performance-critical components still rely on low-level machine code. The flaw in OpenJDK’s x86-64 Base64 decoder allows specially crafted input to bypass memory boundaries, enabling attackers to leak sensitive heap data — similar to Heartbleed — or execute arbitrary code via routine web requests and authentication flows.
Calif, which played a leading role in uncovering the high-profile PHP2Shell memory-safety vulnerabilities that surfaced last month, said the vulnerability was discovered rapidly through AI-driven code auditing.
“It took our own Quang Luong an hour to discover the vulnerability, and two more hours to develop the first working exploit,” the company said in a technical blog post. “The total token cost was less than $200.”
Widespread enterprise exposure
In testing, Calif demonstrated remote code execution against unpatched instances of several widely deployed enterprise applications in their default configurations, including pre-authentication exploits in Atlassian Jira, Confluence, Jenkins, JFrog Artifactory and Keycloak , as well as post-authentication attacks against Apache Kafka Broker, Apache Solr and Elasticsearch.
The Swiss National Cyber Security Centre (NCSC) noted that the list isn't exhaustive. “Other Java applications, including banking software and other industry-specific solutions, can also be affected. Operators must clarify their exposure with their software suppliers,” the NCSC said.
“If successfully exploited, the vulnerability could allow an attacker to operate with the same privileges as the affected application, potentially providing access to sensitive data, credentials, cloud resources, identity systems or software development infrastructure,” said Justin Moore, director of adversary operations at Arctic Wolf.
“For organizations that rely on these applications to manage critical business functions, the downstream impact may extend well beyond the initially compromised system,” he said.
Saeed Abbasi, manager at Qualys’ threat research unit, warned that code execution is not the only outcome. “A successful exploit chain can read Java heap memory before it runs any attacker code,” he said. “That memory can hold private keys, tokens and personal data. CISA also warns that crafted input can crash the JVM, so availability is at risk too.”
Despite the vulnerability’s high severity score, security researchers note that its real-world exploitability is limited due to strict hardware, software and application requirements.
“The nature of this bug makes it slightly more difficult to monetize for cybercriminals, but this buys you days, not months,” said Chris Fistonich, senior manager of Malwarebytes Threat Labs.
CISA Actions and Recommendations
Oracle and the OpenJDK Vulnerability Group released coordinated patches for CVE-2026-114938 on Nov. 17, with Calif holding back its full technical write-up until the fixes went live.
In a news alert, CISA strongly urged organizations to immediately patch the Java4Shell vulnerability and take the following action:
- Identify affected Java installations. Review your software inventory for JDKs and Java runtimes, including those bundled with third-party applications.
- Apply patches. Java and vendor patches should be implemented as soon as they are available, prioritizing internet-facing systems.
- Review Oracle’s security advisory. Refer to the documentation for guidance on patching and affected products and versions.
- Monitor for indicators of suspicious activity. Indicators of compromise include rogue runtimes, unexpected JVM crashes and suspicious Java processes.
“If immediate patching is not feasible, implement temporary compensating controls, such as restricting and validating Base64 input at the application boundary, enforcing input-size limits and limiting unauthenticated access,” CISA advised.
In guidance to individuals and end users, the NCSC said: “Promptly install available security updates for your programs and devices using official update functions. Depending on the product, embedded Java components are updated through a software or device update.”
The disclosure timeline is shrinking
Java4Shell arrives as security dynamics shift rapidly under the pressure of AI. Google recently warned that AI threats have crossed a significant threshold, with attackers now fully automating vulnerability research and exploitation with zero human intervention.
In response, tech giants like Google and Anthropic announced they are slashing coordinated vulnerability-disclosure timelines — compressing traditional 90-day embargoes down to as little as 30 days.
“A vulnerability reported today presents a much higher immediate risk to users than one reported last year,” said Natalie Silvanovich, security engineer at Google Project Zero. “Aspects of our policy that require vendor negotiation or agreement, including determining whether a bug is fixed and whether a grace period applies, are quickly becoming unmanageable.”
Malwarebytes' Fistonich emphasized how this changes the defender’s position. “The bottleneck has shifted,” he said. “Finding critical bugs used to be the slow, expensive part. Now, with AI tools, it's the rapid part, and patching is where we're falling behind. This is very likely to be the new normal and not merely a one- or two-off event.”
If patching is where defenders are now falling behind, some argue the more durable fix is reducing what needs patching in the first place.
Reflecting on how the bug was uncovered, Calif said the incident underscores a deeper architectural problem in modern software: bloated codebases carrying unused dependencies. The company issued a call for what it terms “vibe uncoding.”
“If you don’t need something, there is little reason to keep it running in your systems,” the company said. “Do you need that hand-rolled assembly Base64 decoder to process a few hundred bytes? Probably not.”
James Walker is lead editor at TechTarget Cybersecurity.