Sixty-four letter A’s and a single equals sign. That is all it takes to break one of the most widely used pieces of software on the planet.
Security researchers have disclosed a critical flaw in Java itself — not in one application, but in the runtime that millions of programs are built on. Dubbed Java4Shell, the bug lets an attacker run their own code on a server without logging in, and it was demonstrated against some of the best-known workplace software in the world. Oracle rushed out a fix on 17 November, and the United States’ cybersecurity agency is now urging organisations to patch immediately.
The flaw, tracked as CVE-2026-114938, sits in the part of Java that decodes Base64 — a standard way of packaging data such as login details and file uploads so it can travel safely between systems. The bug is in hand-written processor code inside the HotSpot Java Virtual Machine, the engine that runs Java programs, where a speed-up for modern Intel and AMD chips goes wrong.
A 65-character trigger that breaks Java

According to the researchers who found it, the security firm Calif, a string of 64 letter A’s followed by a single “=” sign makes the decoder write 62 bytes past the end of its output array. That overflow corrupts the program’s memory — and from there, a skilled attacker can seize control of the application entirely.
Calif demonstrated the attack working without any login at all against default installations of six widely deployed products: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. The firm says it also achieved code execution after logging in against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
The name is a deliberate echo of Log4Shell, the Java flaw from December 2021 that set off a global patching scramble. Like that bug, this one is dangerous precisely because it is not in one company’s product — it is in the platform underneath them all. Java powers a huge share of the world’s enterprise software, from banking and telecoms to government and company systems, so a flaw in the runtime reaches everywhere at once.
Which systems are at risk — and which are safe
The flaw affects OpenJDK from version 17.0.6 onwards, including Java 21, 25 and 27, as well as Oracle’s Java 8 Enterprise Performance Pack. But it only bites on a particular kind of hardware: x86-64 processors with a feature called AVX-512 VBMI, found in Intel Xeon chips from Ice Lake onwards and AMD EPYC and Ryzen chips from Zen 4 onwards. Servers running on ARM64 chips are not affected.
Calif rates the flaw 9.2 out of 10 under the CVSS 4.0 scoring system — squarely critical. Oracle, which maintains Java, scores it 8.1 under the older CVSS 3.1 scale and describes it as difficult to exploit, because turning the memory corruption into a working attack on any given application takes tailored work. There is no single universal exploit, Calif says — each target needs its own approach.
That is cold comfort for administrators. The researchers have already shown the attack works against real products in their default settings, and they are deliberately holding back their product-specific exploits to give users time to upgrade. The working exploits, they say, will be published later.
Found with AI — in about an hour
There is a striking twist to how the flaw was found. Calif says its researcher Quang Luong used OpenAI’s Codex coding assistant to audit OpenJDK’s internals, and that it took about an hour to discover the vulnerability and two more hours to build the first working exploit. Rival firm Wiz says its Atlas AI research system produced a working proof-of-concept within two hours, and confirmed remote code execution against Jira, Confluence and Jenkins.
Oracle credits Luong and fellow Calif researcher Albert Yang with reporting the flaw. The disclosure itself leaked ahead of the planned coordinated announcement, and Calif went public on 17 November, publishing its full technical write-up once Oracle’s patch was out.
There is also a client-side sting in the tail. A researcher known as samczsun shared an exploit in which a Java program that connects over the internet to a server controlled by an attacker can itself be compromised — even if that program offers no service of its own. Calif also built a related technique for reading a program’s memory, which it calls JavaBleed.
What to do right now
Oracle released fixed builds on 17 November as part of its November Critical Security Patch Update, which covers 11 Java flaws in total. Amazon has shipped a fixed version of its Corretto Java distribution. As of the morning of 18 November, Eclipse Temurin, Azul Zulu, Microsoft, Red Hat and the Linux distributions had not yet published their fixes.
The advice from CISA, the US Cybersecurity and Infrastructure Security Agency, is blunt: patch immediately. Its alert, issued on 17 November, tells organisations running affected Java versions to upgrade to the fixed builds as soon as they are available from their vendor.
Where patching has to wait, there is a workaround. Starting the Java Virtual Machine with the flag -XX:-UseBASE64Intrinsics switches off the faulty speed-up and closes the exposure — though updating the runtime remains the only complete fix.
As of 17 November, no vendor, government agency or security firm had reported the flaw being exploited in the wild, and it has not been added to CISA’s list of known exploited vulnerabilities. That is the good news. The bad news is that the clock is now running: the researchers have shown the attack works, the patch is out, and anyone who delays is betting that attackers are slower than they are.
Most Popular
How-ToPTA Tax Calculator 2026: Check Mobile Tax on Any Phone420 views
Pakistan NewsPIA Boeing 787 Lease Deal: What It Means for the Airline396 views
Canada JobsTech Jobs in Canada: Roles, Salaries, and Skills Needed392 views
SportsUEFA Champions League 2026-27: Format, Teams and Schedule389 views
TechnologyPM Shehbaz Sets November Deadline for Alibaba AI and Digitalisation Projects in Pakistan369 views
ShowbizWomen’s Fashion in Pakistan 2026: Trends, Brands and Style Guide366 views







