---
title: "AI found the 9.2 Java flaw beneath Jira and Confluence for under $200; Atlassian can't patch it"
description: "Calif used OpenAI's Codex to find Java4Shell, rated 9.2 by its finders and 8.1 by OpenJDK, and reached default installs of Jira, Confluence, Jenkins and Keycloak with no login. The bug sits in Java, not in Atlassian's code, so Atlassian's 318-entry November bulletin cannot list it, and the patch clock sits with distributors that shipped days after Oracle."
publisher: "The Inference"
section: "Security"
published: 2026-11-20T15:32:43.646Z
modified: 2026-11-20T15:32:43.646Z
canonical: https://theinference.org/article/ai-found-the-9-2-java-flaw-beneath-jira-and-confluence-for-under-200-atlassian-can-t-patch-it
language: en
keywords: "Security, Atlassian, Java, Vulnerabilities, OpenAI"
---

# AI found the 9.2 Java flaw beneath Jira and Confluence for under $200; Atlassian can't patch it

> Calif used OpenAI's Codex to find Java4Shell, rated 9.2 by its finders and 8.1 by OpenJDK, and reached default installs of Jira, Confluence, Jenkins and Keycloak with no login. The bug sits in Java, not in Atlassian's code, so Atlassian's 318-entry November bulletin cannot list it, and the patch clock sits with distributors that shipped days after Oracle.

Calif, a security startup, found the Java runtime flaw it calls Java4Shell after about an hour of prompting [OpenAI](https://theinference.org/markets/companies/openai)'s Codex, and built a working exploit in two more [1][2]. Finding the flaw cost under $200 in AI tokens; fixing it means replacing the Java runtime and restarting every server that runs an affected build [1][2]. The exploit takes over default installations of Jira, [Atlassian](https://theinference.org/markets/companies/atlassian)'s project tracker, and Confluence, its wiki, plus the build server Jenkins and the identity server Keycloak, without a login [1][2].

Atlassian, the Australian software company behind those products, reported $1.772 billion of revenue in the September quarter [3], and [from December 3 it starts charging for AI and automation usage](https://theinference.org/article/agents-now-create-more-than-half-of-linear-s-issues-as-atlassian-starts-usage-based-jira-billing-dec-3) [4]. The flaw sits in the self-hosted Data Center products behind that repricing.

*Chart: **Atlassian's quarterly revenue has grown 57% since mid-2024** Line chart of Atlassian quarterly revenue from the June 2024 quarter to the September 2026 quarter, rising from $1.13 billion to $1.77 billion*

*Atlassian's quarterly revenue, US$ billions, for the ten quarters to the period ended September 30, 2026, as reported in its SEC filings. The September 2026 quarter is the $1.772 billion the draft cites, the base on which the December 3 AI and automation metering lands. [10]*

## The flaw sits one layer below Atlassian's patch list

The bug is in the Java runtime itself, one layer below any application's code: hand-written assembly that HotSpot, the virtual machine at Java's core, uses to speed up Base64 decoding, but only on x86-64 processors that carry AVX-512 VBMI, a speed feature on recent [Intel](https://theinference.org/markets/companies/intel) and [AMD](https://theinference.org/markets/companies/amd) server chips [1]. ARM servers, including [AWS](https://theinference.org/markets/companies/amazon) Graviton, are unaffected [1][5]. A single padding character makes the routine write 62 bytes past its output buffer and corrupt the heap [1]. The decode runs on authentication headers and web tokens before any login, which is what makes the flaw pre-authentication [1].

Calif rates it 9.2 under CVSS 4.0; OpenJDK's advisory scores it 8.1, because exploitation needs per-target work [1][2]. Calif published a trigger but is withholding the weaponized per-product exploits [1][2]. That restraint is one reason the window is quiet: GreyNoise has logged more than 150 probes shaped like attacks and seen no successful intrusion [5].

## A 318-entry bulletin that cannot name it

Atlassian's [monthly security bulletin](https://gbhackers.com/atlassian-releases-november-2026-security-updates/), published November 17, lists 318 vulnerability entries across Jira, Confluence and Bitbucket [6]. It cannot list this one: the flaw runs in the Java on the customer's own server, so only the runtime's distributors can patch it [1][6]. Atlassian's guidance on November 19 for its Data Center products was a workaround that disables AVX-512, with product patches still to come; cloud customers were told to do nothing [5].

The other door into the same products is already open. The Apache Axis flaw in Confluence Data Center is being exploited, and [Rapid7 watched one intrusion reach a production cloud data warehouse and Microsoft 365](https://theinference.org/article/rapid7-watched-attackers-go-from-atlassian-s-confluence-to-a-cloud-warehouse-in-four-hours) [7][8]. It carries a December 2 deadline on the [known-exploited list kept by CISA](https://securityaffairs.com/203504/hacking/u-s-cisa-adds-apache-axis-vanderbilt-redcapberriai-litellm-and-synology-dsm-flaws-to-its-known-exploited-vulnerabilities-catalog.html), the US Cybersecurity and Infrastructure Security Agency [7]. Two pre-authentication routes into one product family, inside a week.

## The patch clock sits with the Java distributors

CISA also urged immediate patching of the Java flaw on November 17, and [cyber policies routinely condition coverage on applying critical patches](https://www.insurancebusinessmag.com/uk/news/cyber/critical-java-flaw-puts-cyber-insurance-patching-duties-in-focus-597808.aspx) within a set window [9]. The failure point is inventory: runtimes bundled inside products and container images rarely appear as separate entries, and Keycloak's own container images carried a vulnerable Java build until patched images shipped on November 19 [5][9].

[Oracle](https://theinference.org/markets/companies/oracle) shipped fixed builds on disclosure day, Amazon within a day, [Microsoft](https://theinference.org/markets/companies/microsoft) and Azul two days later [1][5]. Eclipse Temurin and Red Hat had shipped none as of November 19; Red Hat says its patches are being fast-tracked [1][5].

*Chart: **Oracle patched on disclosure day; Microsoft and Azul two days later** Bars chart of days from disclosure to a patched JDK build: Oracle 0, Amazon Corretto 1, Microsoft 2, Azul 2*

*Days from Calif's November 17, 2026, disclosure until each distributor had a patched JDK build, as reported by November 19. Eclipse Temurin and Red Hat had shipped none; Red Hat says patches are being fast-tracked. [1][5]*

The tell: whether Atlassian names the fixed Java build its Data Center products should run. The dates to watch are December 2, the CISA deadline on the Axis flaw [7], and December 3, when the AI and automation metering starts [4]. The bulletin cannot carry this bug. A named build would at least tell customers whose maintenance window they are on.

## Takeaway

A find that cost under $200 in AI tokens opens default Jira, Confluence, Jenkins and Keycloak installs without a login, and the fix sits with the Java distributors, not with Atlassian's 318-entry bulletin.

## Sources

1. [Cyber Kendra, Java4Shell (CVE-2026-114938): Java Base64 Flaw Enables Pre-Auth RCE in Jira, Jenkins and Keycloak, 18 November 2026](https://www.cyberkendra.com/2026/11/cve-2026-114938-pre-auth-rce-flaw-in-java-17-puts-servers-at-risk.html)
2. [BleepingComputer, Critical Java4Shell flaw allows RCE attacks on major Java applications, 17 November 2026](https://www.bleepingcomputer.com/news/security/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications/)
3. [Atlassian Corporation, quarterly figures from its SEC filings, retrieved 20 November 2026](https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001650372)
4. [TechRepublic, Atlassian Will Meter Rovo and Automation Dec. 3: What Admins Need to Budget, 3 September 2026](https://www.techrepublic.com/article/news-atlassian-rovo-automation-pricing/)
5. [SecurityWeek, Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories, 19 November 2026](https://www.securityweek.com/java4shell-exploitation-attempts-begin-as-vendors-rush-out-advisories/)
6. [GBHackers, Atlassian Releases November 2026 Security Updates Fixing 318 Vulnerabilities Across Enterprise Products, 18 November 2026](https://gbhackers.com/atlassian-releases-november-2026-security-updates/)
7. [Security Affairs, U.S. CISA adds Apache Axis, Vanderbilt REDCap, BerriAI LiteLLM, and Synology DSM flaws to its Known Exploited Vulnerabilities catalog, 19 November 2026](https://securityaffairs.com/203504/hacking/u-s-cisa-adds-apache-axis-vanderbilt-redcapberriai-litellm-and-synology-dsm-flaws-to-its-known-exploited-vulnerabilities-catalog.html)
8. [Cyber Daily, Patch now! Hackers targeting critical vulnerability impacting Atlassian, N-able products, 17 November 2026](https://www.cyberdaily.au/security/14450-patch-now-hackers-targeting-critical-vulnerability-impacting-atlassian-n-able-products)
9. [Insurance Business, Critical Java flaw puts cyber insurance patching duties in focus, 18 November 2026](https://www.insurancebusinessmag.com/uk/news/cyber/critical-java-flaw-puts-cyber-insurance-patching-duties-in-focus-597808.aspx)
10. [Atlassian, quarterly figures from its SEC filings, retrieved 20 November 2026](https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001650372)


---

AI found the 9.2 Java flaw beneath Jira and Confluence for under $200; Atlassian can't patch it — The Inference. Canonical: https://theinference.org/article/ai-found-the-9-2-java-flaw-beneath-jira-and-confluence-for-under-200-atlassian-can-t-patch-it
