Guide · Server security

Java4Shell: who is affected and how to check

At 9pm UK time on 17 November 2026, Oracle and the OpenJDK project fixed a flaw in Java itself. The researchers who found it say it let them take over Jira, Confluence, Jenkins and other business software without logging in, and the headlines followed. The real picture is narrower: it needs a recent Java and a particular kind of processor. Here is what happened, what the headlines got wrong, and how to tell in a few minutes whether any of it applies to you.

By Dan · Published 18 November 2026 · 9 min read

The short answer

  • The flaw is in Java, not in Jira or any one app. It is fixed in Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
  • It needs three things at once: Java 17 or newer, an Intel or AMD server chip with a feature called AVX-512 VBMI, and software that decodes data sent in from outside.
  • Java 8 and 11, ARM servers and Apple Silicon Macs are not affected.
  • No attacks had been confirmed when we checked on 18 November, and nobody has reported a data breach.
  • Self-hosted Jira, Confluence and Elasticsearch carry their own Java, so updating the server's Java alone does not fix them.
What happened

What is Java4Shell?

Java4Shell is a flaw in the part of Java that decodes Base64, tracked as CVE-2026-114938. Base64 is a way of writing any data as plain letters and numbers so it can travel inside web requests, login tokens and settings files, and Java programs decode it all the time, often before anyone has signed in. On processors with a set of instructions called AVX-512 VBMI, Java takes a fast route through its decoder, and that route mishandles the end of the text. A string as short as 65 characters makes Java write past the end of the memory it set aside.

It was found by Quang Luong of Calif, the security firm that also disclosed October's PHP2Shell flaws. Calif says Luong set OpenAI's Codex to work on Java's code, found the bug in about an hour, had a first working exploit two hours later, and spent under $200 on AI usage. Oracle credits a second person, Albert Yang, for the same flaw.

Oracle and OpenJDK released fixes at 21:00 UTC on 17 November, in Oracle's monthly patch update, and Calif published its write-up minutes later. It says it ran commands without a login on default installs of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and with a login on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker, and that the list is not complete. It also showed a Java program being attacked simply by connecting to a malicious server. The US agency CISA issued an alert urging organisations to patch.

Calif published only a safe test that shows whether a system has the bug, and says it will publish its working exploits once people have had a chance to upgrade. Datadog and VulnCheck have reproduced the memory corruption and say a burst of requests is enough to crash an unpatched Java service. A takeover is much harder: Calif says every target needs its own tailored attack. The UK's National Cyber Security Centre had published nothing on it when we checked.

Java4Shell at a glance
NameCVE-2026-114938, nicknamed Java4Shell
Where the bug livesJava itself: the part of the OpenJDK runtime that decodes Base64. Not Jira, not Jenkins, not any one app
What an attacker getsA crash is easy. Running commands on the server, with no login, is possible but needs an attack built for each application
Java versions17 (from 17.0.6, January 2023), 21, 25 and 27. Ordinary Java 8 and 11 are not affected
ProcessorsOnly x86-64 chips with AVX-512 VBMI: Intel Ice Lake and later Xeons, AMD Zen 4 and later. ARM is not affected
Fixed in17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, released 17 November 2026
Rating8.1 High from Oracle and OpenJDK (CVSS 3.1). Calif says 9.2 Critical (CVSS 4.0)
Exploited?No confirmed attacks and not on CISA's exploited list when we checked on 18 November
How serious

Is Java4Shell a Jira data breach?

No. Figures read on the evening of 18 November 2026, the day after the fix, and GreyNoise's again on 20 November.

11

products Calif says it took over, six of them without a login, from a list it calls incomplete

Source: Calif

4

Java versions affected: 17, 21, 25 and 27. Ordinary Java 8 and 11 are not

Source: OpenJDK advisory

0

successful break-ins seen by GreyNoise, from 197 probing requests from seven addresses

Source: GreyNoise, 20 November

Nobody has reported a breach, a victim or a compromised system. The flaw was not on CISA's list of vulnerabilities exploited in real attacks, and CISA's own rating on the CVE record says exploitation none. The story spread fast on social media, and some of what is going round is wrong or stretched:

What is being said, and what the sources say
The claimWhat the sources say
“It is a Jira data breach”No breach, victim or compromised system has been reported by anyone. GreyNoise counted zero successful break-ins.
“A flaw in Jira”The flaw is in Java. Jira is one of eleven products Calif named, and Calif says its list is not complete. Atlassian had said nothing when we checked.
“Only some releases of Java 21, 25 and 27”Every release of 21, 25 and 27 before the fix is affected, and Java 17 from 17.0.6 onwards.
“Fixed in 17.0.21.0.3, 21.0.13.0.3 and so on”Those are the last affected Oracle builds. The fixed ones end in .1: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
“AI found it in an hour”A researcher directing OpenAI's Codex found it in about an hour and built a first working exploit in two more, for under $200 of AI usage, Calif says. A person steered it.

The severity score is disputed too. Oracle and OpenJDK rate it 8.1, High, because they rate an attack as hard to pull off. Calif scores it 9.2, Critical, on the newer CVSS 4.0 scale, and Red Hat rates it 9.8, Critical. All agree it needs fixing.

Who it hits

Who is affected by Java4Shell?

A machine is exposed only when all three of these are true. If any one is false, the faulty code never runs.

1. Java 17 or newer

Java 17 from 17.0.6 onwards, and every release of 21, 25 and 27 before the fix. Plain Java 8 and 11, still common on older systems, do not contain the faulty code. The one Java 8 exception is Oracle's paid Enterprise Performance Pack build.

2. A processor with AVX-512 VBMI

Java only takes the faulty route on x86-64 chips with this instruction set: Intel Xeons from Ice Lake on (Sapphire, Emerald and Granite Rapids too) and AMD from Zen 4 on. Older Skylake and Cascade Lake Xeons, ARM servers and Apple Silicon never run it.

3. Software that decodes outside data

The attack needs Base64 sent in from outside to reach Java's decoder. Calif says that happens before login in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Keycloak confirms it decodes Base64 on requests that arrive before anyone signs in.

The trap: apps that bring their own Java

Several of the named products ship with a copy of Java inside them. Updating the Java on the server does nothing for those copies, and each needs its own update from the vendor. This is where a patched-looking server can still be exposed. Here is where each stood on the evening of 18 November, with Keycloak's update of 19 November.

The named products: bundled Java and vendor statements, 18 November 2026
ProductBrings its own Java?Vendor statement
Jira and Confluence (self-hosted)Yes, if installed with Atlassian's installer: a bundled Temurin Java (21 for Jira, 25 for Confluence)None from Atlassian
Jira and Confluence (Atlassian Cloud)Atlassian runs the servers, so nothing for you to installNone from Atlassian
JenkinsNeeds Java 21 or 25. The Windows installer uses the Java already on the machine; the Docker images carry their ownNone
KeycloakContainer images carry their own. 26.8.2-1 and 26.8.2-2 bundle an affected 21.0.13Yes, 18 Nov, updated 19 Nov: fixed image 26.8.2-3 (also tagged 26.8.2, 26.8 and latest) bundles OpenJDK 21.0.13.1. Pull it, or use the workaround in step 5
ElasticsearchYes, by default, and Elastic keeps it up to dateYes, 18 Nov: 7.17.3 and later affected. A user with read access can run code, and anyone can crash a node. Fix due in 8.19.26, 9.4.10, 9.5.7 and 9.6.0; use the step 5 setting until then
JFrog ArtifactoryNot confirmedNot confirmed: JFrog's pages would not load for us
PingFederateNot confirmedNone found

For most small businesses none of this runs in the office: Jira and Confluence are usually rented from Atlassian's cloud, and Atlassian ended support for its Server editions in February 2024. The businesses that need to act are the ones that host their own, such as software firms running Jenkins or Artifactory, companies with their own sign-in system on Keycloak, and anyone with a self-hosted Jira or Confluence Data Center.

What to do

How to check your business, in six steps

Steps one to three are a few commands or one email to whoever runs your servers. If step one turns up nothing, you can stop there.

  1. List everything you run that uses Java

    Think of self-hosted Jira or Confluence, Jenkins, Keycloak, Artifactory, PingFederate, Elasticsearch, Solr or Kafka, and any in-house app built on Spring Boot or Struts. If an IT company looks after your systems, ask them: “Do we run anything on Java 17 or newer, and has it been patched for CVE-2026-114938?” Anything you only use as a cloud service, such as Jira in Atlassian's cloud, is the provider's job to patch.

  2. Check the processor, on the host itself

    On a Linux server, Red Hat's check is grep -o avx512vbmi /proc/cpuinfo | head -1. If it prints nothing, the faulty code never runs on that machine. A container sees the processor of the server it runs on, so check the server, not the image. In the cloud, Red Hat lists AWS C6i, M6i, C7i and M7i, Google Cloud C3 and C4, and Azure Dsv5 and Dsv6 among the families most likely to be affected. AWS Graviton and older families such as M5 and T3 are not.

  3. Check the Java the service actually uses

    Run java -version for the exact Java each service starts with, not just the one on your path. You want 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or later. Your distributor's number may look a little different: the table below the steps gives each one.

  4. Update, including the copies apps carry themselves

    Updating the server's own Java does not fix an app that brought its own. Jira and Confluence installed with Atlassian's installer, Elasticsearch, Keycloak containers and the Jenkins Docker images each need their own update from the vendor. Do not swap in a different Java unless the vendor's instructions say you can. Restart afterwards: a running Java service keeps the old code until it restarts.

  5. If you cannot patch yet, switch off the fast decoder

    Start Java with -XX:-UseBASE64Intrinsics. Red Hat calls it the preferred workaround and Keycloak and Elastic recommend it, but Oracle and OpenJDK do not mention it, so treat it as a stopgap. It needs a restart. Red Hat's alternative, -XX:UseAVX=2, switches off the chip feature altogether and is for x86-64 servers only: Red Hat says Java on ARM64 will not start with it. Keep these systems off the open internet where you can. Cloudflare's new rules are on paid plans but set to log, not block, and the free plan had no rule yet when we checked.

  6. Patch before the exploits are published

    Calif says it will publish its working exploits later, with no date given. GreyNoise says attacks may stay narrow until then, because each application needs its own exploit. Meanwhile, an unexplained crash of a Java service on an unpatched machine is worth a look: crashing it is the easy part.

The fixed builds, by distributor

Most servers get Java from a distributor rather than from Oracle, and each numbers its builds a little differently. When we checked on 20 November, Ubuntu and Debian had shipped fixes in their security updates, and Red Hat had not.

Fixed builds by distributor, as checked on 18 November 2026
DistributorFixed versionReleased
Oracle JDK17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 (and 8u513 for the paid Java 8 Performance Pack)17 Nov
Amazon Corretto17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.417 Nov
Azul Zulu17.70.201, 21.54.201, 25.38.201, 27.30.20117 Nov
Microsoft Build of OpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1 (Microsoft does not ship 27)18 Nov
BellSoft Liberica17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.118 Nov
Eclipse Temurin17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, 27.0.1.1+4 on Linux; Windows for 21 and 25 only so far; Docker images not yetPartial
Red Hat (RHEL)Not yet. Red Hat says it is expediting fixesPending
UbuntuFixed for openjdk-17, 21 and 25 on every supported release (older releases through Ubuntu Pro)By 20 Nov
DebianFixed in bookworm (openjdk-17) and trixie (openjdk-21 and 25) security updates; forky not yetBy 20 Nov

Java 18 to 20, 22 to 24 and 26 are out of support and will get no fix. Nobody has confirmed whether they contain the faulty code, but anything still on one of them is overdue a move to a supported version anyway.

What is not settled yet

What we do not know yet

How easy a takeover really is. Only Calif has shown one in public, and it is keeping the code private for now. VulnCheck says it has a working exploit for paying customers, and another firm, Upwind, has claimed one on social media. Nobody has verified either. Everyone who has tested it agrees a crash is easy.

What the vendors will say. Atlassian, Jenkins, JFrog and Ping Identity had published nothing we could find. Keycloak's fixed image, 26.8.2-3, came out on 19 November, while Elastic's fixed releases had not shipped.

When the exploits come out. Calif gives no date. GreyNoise says mass attacks may stay difficult until exploit code for widely used applications is released, which would be the moment the risk changes. We will update this page as the vendors and the exploit picture move.

FAQ

Java4Shell questions, answered

What is Java4Shell?

Java4Shell is the nickname for CVE-2026-114938, a flaw in the part of Java that decodes Base64 text. On servers with a particular Intel or AMD processor feature, a specially shaped piece of Base64 makes Java write past the end of the memory it set aside. The researchers who found it, at the security firm Calif, say that let them run commands without logging in on default installs of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. Oracle and the OpenJDK project fixed it on 17 November 2026.

Is Java4Shell being exploited?

Not that anyone had confirmed when we checked on the evening of 18 November 2026. It was not on CISA's Known Exploited Vulnerabilities list, CISA's own rating on the CVE record said exploitation none, and by 20 November GreyNoise had seen 197 probing requests from seven addresses, still with no successful break-in. Crashing an unpatched Java service is easy, though, and Calif says it will publish its working exploits later.

Which Java versions are affected by CVE-2026-114938?

Java 17 from 17.0.6 onwards, and every release of Java 21, 25 and 27 before the fix. The fixed versions are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, or the matching build from your distributor. Ordinary Java 8 and Java 11 are not affected. The only affected Java 8 build is Oracle's paid Enterprise Performance Pack, fixed in 8u513.

I use Jira or Confluence. Do I need to do anything?

In Atlassian's cloud, no: Atlassian runs the servers, so there is nothing for you to install. Self-hosted Jira and Confluence Data Center are different. Atlassian's installer brings its own Java (Eclipse Temurin 21 for Jira, 25 for Confluence), so updating the server's Java does not fix them and they need Atlassian's own update. Atlassian had published nothing about Java4Shell when we checked on 18 November.

How do I check whether my processor is affected?

On a Linux server, run grep -o avx512vbmi /proc/cpuinfo | head -1. If it prints avx512vbmi, the faulty code can run there; if it prints nothing, it cannot. That means Intel Xeons from Ice Lake onwards and AMD from Zen 4 onwards. ARM chips, AWS Graviton and Apple Silicon included, are not affected.

Is Java on my laptop at risk?

Usually not. VulnCheck notes that Intel switched AVX-512 off on its laptop and desktop chips from the 12th generation onwards, Apple Silicon Macs are ARM, and Java 8 is not affected. Machines with AMD Ryzen 7000 or 9000 chips, or Intel laptop and desktop chips from 2019 to 2021, do have the feature. Calif also showed that a Java program which connects to a malicious server can be attacked, so keep desktop Java 17 or newer updated too.

Is my website affected by Java4Shell?

Almost certainly not, unless something behind it runs Java. WordPress runs on PHP, and Next.js sites like the ones we build run on Node.js, so neither contains the faulty code. A site that uses a self-hosted Elasticsearch for its search, or a booking system written in Java, is worth checking with whoever runs it.

Is Java4Shell the same as Log4Shell?

No. Log4Shell (CVE-2021-44228, December 2021) was a flaw in Log4j, a logging library that many Java programs include, and the fix was a new Log4j. Java4Shell is in the Java runtime itself, so the fix is a new Java, and it only affects certain processors.

References

Sources & further reading

The guidance on this page is grounded in primary sources. Follow the links to read them in full.

Not sure what your website runs on?

The sites we build run on Next.js, with no Java and no PHP underneath, so a flaw like this one has nothing to land on. If you are not sure what sits behind your site, tell us the address and we will find out.