Skip to main content
Intelligence Library
Threat IntelligenceLive

Java4Shell: Critical OpenJDK RCE Vulnerability (CVSS 9.2)

A flaw in Java's Base64 decoder gives unauthenticated attackers remote code execution in Keycloak, Jira, Confluence, Jenkins and more. We are tracking developments as they happen.

Java4Shell (CVE-2026-114938, CVSS 9.2) is a heap memory corruption flaw in the OpenJDK Base64 decoder affecting Java 17.0.6 and later, including 21, 25 and 27, on x86-64 CPUs with AVX-512 VBMI. It allows unauthenticated heap disclosure and remote code execution. Oracle released fixes on 17 November 2026 and other vendors are following. Patch internet-facing identity and CI/CD systems first, or disable the intrinsic with -XX:-UseBASE64Intrinsics until you can.

Published
Updating live, last update
Precursor Security
Also unfolding: NGINX2Root (CVE-2026-123007), critical nginx HTTP/2 flaws enabling unauthenticated RCE. Follow our nginx live blog.

What you should do now

  1. Inventory every JVM, including runtimes bundled inside vendor products and appliances. Operating system updates do not patch bundled runtimes.
  2. Patch internet-facing identity and CI/CD first: Keycloak and PingFederate, then Jira, Confluence, Jenkins and Artifactory, then any other Java service handling logins, tokens or uploads.
  3. Restart and rebuild. A new package with an old JVM still running is still vulnerable. Recreate containers from patched images.
  4. Cannot patch today? Add -XX:-UseBASE64Intrinsics and restart, or take the service off the internet or behind a VPN.
  5. Do not forget clients. Java programs making outbound TLS connections can be exploited by a malicious server.
  6. Hunt for signs of attempts: JVM crashes and hs_err_pid files, Base64 decoder exceptions, and Java processes spawning shells or new outbound connections.

Java4Shell live timeline

18 Nov 2026Pinned

What we know so far

A critical memory corruption flaw in OpenJDK's Base64 decoder, tracked as CVE-2026-114938 and nicknamed Java4Shell, lets an unauthenticated attacker overwrite Java heap memory, read secrets from it and reach remote code execution. Fixes shipped last night in Oracle's November Critical Security Patch Update; other Java vendors are still rolling out.

Severity

CVSS 9.2

v4.0 (Calif, OpenJDK). Oracle rates it 8.1 on v3.1.

Impact

Pre-auth RCE

Plus heap memory disclosure

CVECVE-2026-114938
ComponentOpenJDK HotSpot x86-64 Base64 decoder intrinsic
Bug classHeap out-of-bounds write (62 bytes)
AffectedOpenJDK 17.0.6 and later (17, 21, 25, 27) on x86-64 CPUs with AVX-512 VBMI
Not affectedStandard Java 8, Java 11, 17.0.0 to 17.0.5, ARM64
AuthenticationNone required
ExploitationExploit attempts seen in the wild (GreyNoise); not yet in CISA KEV
FixOracle November 2026 CSPU; other vendors rolling out

How it works: hand-written assembly that speeds up Base64 decoding using AVX-512 miscalculates the padding on a short, malformed string ending in an equals sign. The decoder then writes a full 64-byte block, 62 bytes past the end of its output buffer, before Java rejects the input. By then the neighbouring heap objects are already corrupted. Calif chained this into a Heartbleed-style memory read it calls JavaBleed, which can leak keys, tokens and personal data before code execution is even attempted.

The flaw has been present in every affected Java release since early 2023. No universal exploit exists: each product needs its own chain, and failed attempts tend to crash the JVM. We will keep this page updated through the day.

18 Nov 2026

Also unfolding today: NGINX2Root, critical nginx RCE flaws (separate live blog)

A second major disclosure landed this afternoon, and it is not connected to Java4Shell. NGINX2Root covers critical flaws in nginx's HTTP/2 handling, led by CVE-2026-123007, that let an unauthenticated attacker run code on the server, with a separate Linux kernel bug taking that to root on the host. Xint, Wiz, Rapid7, Metnir and Ikotas Labs found them independently, and Wiz and Rapid7 score them CVSS 4.0 9.2.

Fixes are out in nginx 1.30.7 (stable) and 1.31.9 (mainline), and NGINX Plus 37.3.0.1 and 37.0.8.1. Because nginx so often sits in front of Java applications, check both today. We are covering it in a separate live blog: NGINX2Root: live nginx RCE updates.

18 Nov 2026

Tenable adds Amazon Linux and Linux distro checks: now eight Nessus plugins

Tenable now has eight Nessus plugins for Java4Shell, up from two this morning. Five new Amazon Linux checks match the AWS advisories in our 15:40 entry: 382347, 382319, 382332 and 382309 for Corretto 17, 21, 25 and 27 on Amazon Linux 2023, and 382312 for Corretto 17 on Amazon Linux 2.

Plugin 382489, "Linux Distros Unpatched Vulnerability", flags hosts whose distribution has not shipped a fix yet, such as Debian and Ubuntu. All eight are local checks, so they need credentialed scans or agents, and none of them check whether the CPU supports AVX-512 VBMI.

18 Nov 2026

BellSoft Liberica ships its November Java4Shell fixes

BellSoft has released its November Liberica JDK builds with the Java4Shell fix. Liberica 21.0.13.1 is now the latest Java 21 build in BellSoft's release data. BellSoft says builds for Java 6, 7, 8, 11, 17, 21, 25 and 27 are out, but the new 17 and 25 builds were not yet listed when we checked, so confirm the version you download is 17.0.21.1, 21.0.13.1 or 25.0.5.1 or later.

Still waiting: Eclipse Temurin, Debian, Ubuntu and RHEL packages.

18 Nov 2026

GreyNoise now lists 10 IPs to block, and three are still firing

This updates our 15:30 entry. GreyNoise has widened its Java4Shell block list to cover any tracked IP classed as malicious or suspicious, and as of 15:48 UTC it lists 10 block candidates.

The ones that matter most are still active. 64.52.111.248, 64.52.111.253 and 64.52.111.255, all Amazon-hosted and tagged as Base64 heap overflow RCE attempts, were last seen between 14:43 and 15:43 UTC. Newly tracked 45.13.212.209 (Data Campus) was last seen at 15:37 UTC and appears across thousands of GreyNoise sensors. Totals are unchanged at 69 requests, with no successful intrusions.

GreyNoise block candidates, 15:48 UTC

  • 34.219.66.59
  • 64.52.111.248
  • 64.52.111.253
  • 64.52.111.255
  • 104.168.35.123
  • 217.138.216.145
  • 134.82.73.91
  • 31.76.87.52
  • 213.230.125.2
  • 45.13.212.209

Block these at your edge and search your web, proxy and WAF logs for them, but patching or -XX:-UseBASE64Intrinsics remains the fix.

18 Nov 2026

Amazon Linux: Corretto fixes are out, but AL2023 may not show them without the new release version

Amazon Linux published fixed Corretto packages on 17 November: ALAS2023-2026-3478 to 3481 for Corretto 17, 21, 25 and 27 on Amazon Linux 2023, and ALAS2-2026-4123 for Corretto 17 on Amazon Linux 2.

The catch: Amazon Linux 2023 locks each host to a release version, so a plain dnf update, or a check filtered by CVE, can report nothing to install while vulnerable Corretto is still present. AWS's advisory gives the fix as dnf update --advisory ALAS2023-2026-3478 --releasever 2023.12.20261117; each Java version has its own advisory number.

Corretto 22, 23, 24 and 26 on Amazon Linux 2023 are marked No Fix Planned, so move those to 21, 25 or 27. Corretto 8 and 11 are not affected. AWS rates the issue Important, with a CVSS 3.1 score of 8.8, lower than the 9.2 used elsewhere.

18 Nov 2026

GreyNoise: more probing, zero intrusions, and no IPs it now recommends blocking

GreyNoise's Java4Shell dashboard (updated 15:18 UTC) now shows 69 Java4Shell-shaped requests from 4 IP addresses since 17 November, up from 53 from 3 this morning. There are still no successful intrusions against its sensors.

Update: GreyNoise has since widened its block list and now lists 10 block candidates, some still active. See the 16:04 entry.

It has also revised its view. 31.76.87.52 (Poland, last seen at 06:26 UTC) is now classed as suspicious rather than malicious, a new address on an Uzbek ISP, 213.230.125.2, is tagged as a scanner check, and the dashboard currently lists no block candidates.

This looks like researchers and scanners probing, not an attack campaign. Keep any blocks you already have, but an IP blocklist is not protection: patch, or apply -XX:-UseBASE64Intrinsics until you can.

18 Nov 2026

Microsoft Build of OpenJDK ships Java4Shell fixes

Microsoft has released fixed builds of its OpenJDK distribution: 17.0.21.1, 21.0.13.1 and 25.0.5.1. Its release notes say they include the fixes from the OpenJDK vulnerability advisory, and they are now the default on the download page. If your apps or container images pin the Microsoft JDK, rebuild and redeploy.

Still waiting: Eclipse Temurin (and the official eclipse-temurin Docker images), Debian, Ubuntu and RHEL packages. Use -XX:-UseBASE64Intrinsics on those until fixes land.

18 Nov 2026

UK NCSC has not issued Java4Shell guidance yet

As of 15:09 GMT, the UK's National Cyber Security Centre has published nothing on Java4Shell, either on its website or on X. That is a contrast with PHP2Shell last month, when the NCSC alerted UK organisations on the first morning. Agencies in the US, Germany, Switzerland, Belgium, France, Japan, Canada and Slovenia have already acted.

UK organisations do not need to wait. CISA's alert and Slovenia's deadlines (see the 15:00 entry) are a sensible baseline: identify affected Java, including bundled runtimes, within 24 hours, and patch internet-facing systems within 48 hours of a fix being available, applying -XX:-UseBASE64Intrinsics until then. We will update this page as soon as the NCSC publishes anything.

18 Nov 2026

Hospitals race to "patch before they hack"; Epic says it is not affected

The New York Times reports that US health networks are scanning internal networks, medical devices and internet-facing systems for affected Java and patching as fast as they can. The American Hospital Association says it is not aware of any impact on hospital operations so far, beyond the disruption of responding. Its national cybersecurity adviser, John Riggi, described the effort as a race to "patch before they hack".

Epic Systems, the largest US health records vendor, said its systems are not affected. Oracle, which owns the Cerner health records business, issued the Java fix on Tuesday. Group purchasers Premier and Vizient say thousands of clients are working around the clock on the response.

For UK healthcare: the same exposure applies to NHS trusts and private providers. Java often sits inside clinical and administrative systems, imaging software and medical device management consoles rather than as a standalone install, so ask suppliers directly whether their products bundle an affected runtime, and apply -XX:-UseBASE64Intrinsics where you control the JVM.

18 Nov 2026

Cloudflare ships six Java4Shell WAF rules, but they only log by default

Cloudflare has released six Java4Shell rules in its Managed Ruleset for Pro, Business and Enterprise plans. They cover malformed Base64 in headers, query values, request bodies, path segments, JWT components and WebAuthn values.

They are enabled in Log mode, not Block, because some legitimate token formats can look like the trigger. Being behind Cloudflare does not protect you until you act: review matches in Security > Security Analytics > Events, then in Security > Settings edit the Cloudflare Managed Ruleset, search for CVE-2026-114938 and set the action to Block. A rule for the Free Managed Ruleset is still in progress.

Header5de9b20a45ea45d3841919ab4d718bf4
Query value46bb4172813e471ea62d31c02337b51d
Body valued4dc3f71f1bc44a0811ae570e5e5836c
Path segment0dceaf0684b54fd0b085fcfb6fd6f152
JWT component0ddd0eb664a040779f2f19065a25d991
WebAuthn value4fce1ea79a614c07a27348d167d74ebb

Cloudflare stresses that a WAF cannot see every path to the vulnerable decoder, such as nested encodings or outbound TLS, so it is an extra layer rather than a fix. It says it has seen no indication of Java4Shell exploitation on its infrastructure.

18 Nov 2026

First binding government order: Slovenia sets 24-hour and 48-hour deadlines

Slovenia's Government Information Security Office (URSIV) has gone beyond an advisory and issued a binding order to organisations covered by its information security law, raising the national threat assessment to high. Its deadlines are a useful benchmark for anyone setting their own:

  • 24 hours: identify affected systems, including products with bundled Java, with internet-facing and identity services first. If you cannot rule a system out, treat it as affected.
  • 48 hours / 7 days: patch internet-facing systems within 48 hours and everything else within seven days, counting from when a fix exists for that distribution or product. Then restart processes or rebuild containers and verify the fixed runtime is actually in use.
  • Meanwhile: apply temporary mitigations within 24 hours, such as disabling the vulnerable functionality and restricting access, or isolate the system from public networks if that is not possible.
  • Monitoring: check for signs of exploitation such as unexpected crashes and unusual connections, and preserve logs.
18 Nov 2026

First EPSS score is low, and why that should not slow you down

FIRST has published the first EPSS score for CVE-2026-114938: 0.73%, around the 55th percentile. That looks reassuring, but EPSS predicts exploitation over the next 30 days from signals such as observed attacks, public exploit code and how a vulnerability is described. A day-old CVE with no confirmed exploitation and withheld product exploits scores low by default, so expect it to move as data arrives.

For Java4Shell, exposure (an affected JDK on an AVX-512 VBMI host) and the trivially easy denial of service matter more than today's EPSS number.

18 Nov 2026

Found while building a phone exploit: how Java4Shell was discovered

Calif researcher Quang Luong told The Record that he discovered Java4Shell while "developing a 0-click exploit on a certain phone vendor". Calif says the hunt then took about an hour with AI assistance, with a first working exploit two hours later for under $200 in AI costs.

It is a reminder of how this class of bug surfaces: researchers chasing high-value targets turn up flaws in shared, foundational code that everything else depends on.

18 Nov 2026

Germany's BSI issues Java4Shell warning, says no known attacks

Germany's Federal Office for Information Security (BSI) has published a security notice, "OpenJDK: critical vulnerability Java4Shell endangers Java applications", rated criticality 2 (High). BSI says there are currently no known attacks involving Java4Shell.

The warning was carried by financial newswires within minutes, a sign the story has reached boardrooms as well as security teams. No known attacks means this is the cheap window: patch, or apply -XX:-UseBASE64Intrinsics, before the first exploitation reports arrive.

18 Nov 2026

GraalVM: Native Image apps built with 25.0 or earlier are not affected

GraalVM says Native Image applications built with GraalVM 25.0 or earlier are not affected by Java4Shell. Applications built with the innovation releases 25.1 and later are, and the fix will ship in GraalVM 25.6, scheduled for 24 November 2026. GraalVM recommends that users of those releases upgrade.

This applies to Native Image binaries only. GraalVM for JDK running as a normal JVM is covered by Oracle's November update, which lists GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3 as affected.

18 Nov 2026

Ubuntu raises Java4Shell to High and confirms which OpenJDK packages are vulnerable

Ubuntu has upgraded CVE-2026-114938 from Medium to High priority ("This is an RCE") and finished its evaluation on its CVE page:

  • Vulnerable: openjdk-17 on every release from 18.04 to 26.10, openjdk-21 from 20.04, openjdk-25 from 22.04 and openjdk-27 on 26.10, plus the CRaC builds of 17, 21 and 25 on 26.04 and 26.10.
  • Not affected: openjdk-8 and openjdk-lts.
  • Fixed: none yet.

Running apt upgrade still will not help today. Use -XX:-UseBASE64Intrinsics until Ubuntu ships updated packages.

18 Nov 2026

16 of 20 popular Java container images still ship a vulnerable JDK

A researcher who checked published container images found that 16 of 20 popular Java images still ship an affected JDK. They include all five products with demonstrated pre-auth RCE:

Keycloak 26.8.2JDK 21
Jira21.0.13
Confluence25.0.5
Jenkins LTSJDK 21
PingFederateJDK 25

Others on the list include Tomcat 10.1, SonarQube, Solr, Kafka, Graylog, Flink, Spark, ZooKeeper, ThingsBoard and OpenSearch. Elasticsearch 9.1.0 bundles JDK 24, a release line that is not among OpenJDK's fixed versions.

What to do: pulling the latest tag today does not fix anything. Until image publishers rebuild on a patched JDK, set -XX:-UseBASE64Intrinsics through JAVA_TOOL_OPTIONS (or the image's own JVM options variable, such as JAVA_OPTS_APPEND for Keycloak) and redeploy.

18 Nov 2026

First WAF rule lands, but the big CDNs have not shipped one yet

CrowdSec has released a free virtual patch, crowdsecurity/vpatch-CVE-2026-114938. It matches the shape of the trigger rather than a specific payload: a Base64 or Base64url token of 32 or more characters ending in = or == whose length is not a multiple of four, which valid Base64 never is.

It checks the Authorization and Proxy-Authorization headers (including each JWT segment), every cookie (such as Keycloak's KEYCLOAK_IDENTITY) and parameters used by public exploits against Keycloak and Jira. To get it now, run cscli hub update and cscli hub upgrade, then restart CrowdSec. CrowdSec is clear that it is a stopgap: it cannot see Base64 decoded from other inputs or from outbound connections.

Unlike PHP2Shell last month, Cloudflare, Akamai, Imperva and Fastly had not published Java4Shell WAF rules when we checked at 13:25 GMT. Update: Cloudflare has since shipped rules for paid plans, set to log by default (see the 15:01 entry). If you rely on a CDN WAF, check its configuration and still apply the JVM flag.

18 Nov 2026

How many systems are really at risk? Estimates put RCE exposure at around 0.12% of JVMs

OX Security has worked through each condition an attacker needs (an affected HotSpot JDK, an x86-64 host with AVX-512 VBMI, untrusted Base64 reaching the decoder before login, internet exposure and a working application-specific chain) and estimates that roughly 0.12% of JVMs, about 12 in every 10,000, are realistic remote code execution targets today. It stresses that these are estimates rather than measurements, and that treating the conditions as independent probably understates the risk, because newer Java versions tend to run on newer CPUs.

Malwarebytes reaches a similar view, calling Java4Shell "a critical flaw with a narrow reach" and noting that home users are unlikely to be affected, since an ordinary PC rarely runs a Java server that accepts Base64 from the internet.

A small percentage is not a small number. The systems that do qualify are disproportionately identity providers, CI/CD servers and collaboration tools, and the much easier denial of service is not limited to that 0.12%.

18 Nov 2026

Hidden Java: UniFi, Minecraft servers and Omnissa bundle their own runtimes

Admins on Reddit are finding Java4Shell-affected runtimes in places most inventories miss. One UniFi user ran Calif's trigger test against the JDK 25 bundled with UniFi Network on an AMD EPYC host and reproduced the memory corruption (62 bytes overwritten); -XX:-UseBASE64Intrinsics stopped it. They traced where UniFi decodes Base64 but found no unauthenticated remote path, so treat it as vulnerable but not proven exploitable.

Minecraft server operators on r/admincraft are being told to add the same flag to every server's startup flags, and Omnissa Horizon admins point out that Connection Servers bundle OpenJDK 17. None of these vendors has published guidance yet.

What to do: if a product ships its own Java, check the bundled runtime version and the host CPU, and add -XX:-UseBASE64Intrinsics to its JVM options until the vendor ships a fix. Operating system updates will not patch a bundled runtime.

18 Nov 2026

java4shell.com and Calif's safe test: check your JDK and CPU in seconds

java4shell.com is Calif's official home for the disclosure and redirects to its full write-up. The domain was registered on 14 November, three days before the vulnerability was disclosed, the same pattern we saw with php2shell.com last month: the brand existed before the public knew there was a bug.

The write-up includes a bounded test program that warms up the decoder, feeds it the malformed input and counts changed bytes inside a real array. It prints REPRODUCED if your JDK and CPU combination has the bug and NOT REPRODUCED (exit code 1) if not. Calif says every write lands inside a real array, so it is safe to run. It does not exploit anything or test whether an application is reachable.

One catch: the test uses the 64-character trigger, but OpenJDK 17 needs 128 characters. On Java 17 it can report NOT REPRODUCED on a vulnerable system, so do not treat a negative result on 17 as an all-clear. As a precaution, run it on a test machine with the same JDK and CPU rather than in production.

What the realistic risk looks like: turning the bug into remote code execution is hard. It needs heap grooming and an application-specific memory leak to get past ASLR, and Calif is still withholding its product exploits. The more immediate impact is denial of service: VulnCheck found that crashing an affected JVM is trivial, with "a simple burst of requests" reliably bringing the service down, and Datadog reached the same conclusion. Unpatched internet-facing Java services can be knocked offline today, even by attackers who never get code execution.

18 Nov 2026

AWS Fargate: whether you are exposed can change from one task to the next

An engineer investigating Java4Shell on AWS ECS Fargate found that x86-64 tasks land on a mix of host CPUs, some with AVX-512 VBMI and some on older Intel Xeons without it. In one service, 12 of 48 tasks had the vulnerable instruction set.

A single task inspection that comes back clean proves nothing for the rest of the service, and the next deployment can land somewhere else. The same applies to any platform where you do not choose the CPU, including serverless containers and autoscaling groups with mixed instance types.

What to do: apply -XX:-UseBASE64Intrinsics across the whole service (for example through JAVA_TOOL_OPTIONS in the task definition) rather than relying on a CPU check, then patch the runtime as soon as a fixed build is available.

18 Nov 2026

Google Cloud masks AVX-512 VBMI for managed Java runtimes; other services need action

Google Cloud bulletin GCP-2026-082 says Google has masked AVX-512 VBMI for managed Java 17, 21 and 25 runtimes on App Engine standard and the Cloud Run second generation execution environment (including 2nd gen Cloud Run functions) until 30 November. Those workloads are protected without customer action, and patched runtime base images are rolling out.

Not covered by that safeguard: Cloud Run first generation, Cloud Functions 1st gen, App Engine flexible, Cloud Run jobs and worker pools, custom containers, GKE workloads, Dataproc and Dataflow. For those, Google recommends setting the following and redeploying:

JDK_JAVA_OPTIONS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"

The -XX:+IgnoreUnrecognizedVMOptions part stops the flag breaking JVMs on ARM nodes, which makes it safe for mixed fleets. GKE control planes and Container-Optimized OS nodes are not affected, and Google says its hypervisors and isolation boundaries between customer workloads are not affected either.

18 Nov 2026

Atlassian, Jenkins and Ping have not published advisories yet

Calif demonstrated pre-authentication RCE in Jira, Confluence, Jenkins and PingFederate, but as of midday none of Atlassian, the Jenkins project or Ping Identity has published Java4Shell guidance. Keycloak is the only affected product vendor with an advisory so far (see the 10:57 entry).

Self-managed Jira and Confluence installs usually run on the Java runtime bundled with the installer, so operating system updates will not fix them. Until the vendors respond, add -XX:-UseBASE64Intrinsics and restart:

  • Jira and Confluence: add it to JVM_SUPPORT_RECOMMENDED_ARGS in setenv.sh (or setenv.bat on Windows).
  • Jenkins: add it to JAVA_OPTS, for example with systemctl edit jenkins.
  • Confirm on the running process with jcmd <pid> VM.flags.

Atlassian Cloud customers cannot apply this themselves and are reliant on Atlassian. We will update this page as vendor advisories land.

18 Nov 2026

More fixed builds: Azul Zulu and Amazon Corretto 21 and 25 now patched

Azul has shipped fixed Zulu builds 17.0.21.1, 21.0.13.1 and 25.0.5.1, and Amazon has added Corretto 21.0.13.1.2 and 25.0.5.1.2 alongside the 17.0.21.1.2 build released yesterday.

Still waiting: Eclipse Temurin (latest builds are from 22 October), Microsoft Build of OpenJDK (since fixed, see the 15:16 entry), and Debian, Ubuntu and RHEL packages. If you can switch distribution, a fixed build is now available for every supported Java line.

18 Nov 2026

Swiss and Belgian cyber agencies tell organisations to patch now

Switzerland's National Cyber Security Centre has published a warning, Java4Shell: Critical Java vulnerability - install security updates immediately, recommending that operators check straight away whether their systems are affected and update them. It stresses that Java is often embedded in software and devices without users being aware of it.

Belgium's Centre for Cybersecurity (CCB) has also issued a warning advising organisations to patch, citing the CVSS 3.1 score of 8.1 and the risk of unauthenticated attackers taking over Java applications.

18 Nov 2026

Containers and Kubernetes: applying the stopgap without rebuilding images

For containerised Java you can apply the stopgap without rebuilding images. Set JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics" in the deployment and restart the pods: the JVM reads the variable at start-up. Unlike -XX:UseAVX=2, this flag is safe on ARM nodes, so it can go into manifests shared across mixed clusters.

  • Append to any existing JAVA_TOOL_OPTIONS value rather than replacing it.
  • Never put -XX:DisableIntrinsic=_base64_decodeBlock there: it stops the JVM starting, and through an environment variable that means every service at once.
  • Confirm it took effect on a running pod with jcmd 1 VM.flags, not just by reading the manifest.

Some images use their own variable instead, such as JAVA_OPTS_APPEND for Keycloak (see the 10:57 entry). Patch and rebuild as soon as a fixed runtime is available for your base image.

18 Nov 2026

JPCERT/CC issues advisory; no attacks confirmed in Japan

Japan's national CERT, JPCERT/CC, has published a CyberNewsFlash on Java4Shell urging organisations to act promptly. It confirms the x86-64 AVX-512 VBMI condition, flags products that bundle their own Java runtime, and points to -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 only, where patching cannot happen immediately.

As of 18 November, JPCERT/CC has not confirmed any real-world attacks exploiting the flaw.

18 Nov 2026

Keycloak: official images ship a vulnerable JDK, no fixed image yet

Keycloak has published its own Java4Shell advisory. Its official x86-64 container images 26.8.2-1 and 26.8.2-2 bundle OpenJDK 21.0.13, an affected build, and Keycloak says it "cannot recommend a specific fixed Keycloak image" until patched OpenJDK builds are available. It also warns not to rely on the Keycloak version number alone to decide whether a deployment is fixed.

Interim fix: disable the Base64 intrinsic, then restart

  • Docker or Podman: -e JAVA_OPTS_APPEND=-XX:-UseBASE64Intrinsics
  • Docker Compose: JAVA_OPTS_APPEND: "-XX:-UseBASE64Intrinsics" in the Keycloak service environment
  • Operator-managed Keycloak: add JAVA_OPTS_APPEND to the keycloak container environment. The Operator itself needs JDK_JAVA_OPTIONS instead.

Append the flag to any existing value rather than replacing it, then check the running JVM: jcmd <pid> VM.flags -all | grep -F UseBASE64Intrinsics should report false. Keycloak is one of the products with a demonstrated pre-authentication RCE, so any internet-facing instance should be changed now.

18 Nov 2026

Researchers expect targeted attacks, not mass exploitation

watchTowr says the CPU, JDK and Base64 prerequisites make application-specific exploits more likely than indiscriminate spraying. GreyNoise agrees it will be hard to mass-exploit, at least initially. Datadog Security Labs, which reproduced the overflow, says crashing the service is the more readily achievable impact, and that reliable code execution needs work tailored to each application.

That does not lower the priority. The realistic risk is targeted attacks on high-value Jira, Jenkins, Keycloak and Confluence servers, which are exactly the systems attackers want, so the patching order stays the same.

18 Nov 2026

Eclipse Temurin has not shipped a fix yet

The Adoptium API still lists 17.0.21+9, 21.0.13+9 and 25.0.5+8, all built on 22 October, as the latest Eclipse Temurin releases. Upwind reproduced Java4Shell on exactly these builds, so anyone on Temurin, including many official Docker images, currently has no patched build to move to.

Until Adoptium ships, start the JVM with -XX:-UseBASE64Intrinsics, or move to a build that already contains the fix, such as Oracle's .1 releases or Amazon Corretto 17.0.21.1.2.

18 Nov 2026

First Java4Shell-shaped traffic seen in the wild, no successful exploitation

GreyNoise has launched a live Java4Shell dashboard. As of 10:18 UTC it had recorded 53 Java4Shell-shaped requests from 3 IP addresses since 17 November, tagged as Base64 heap overflow RCE attempts, with no confirmed successful exploitation against its sensors. Most of the related infrastructure sits on Amazon (AS16509), with the rest in Germany (M247), Poland and the US.

IPs GreyNoise tagged as malicious at 10:18 UTC

  • 31.76.87.52
  • 217.138.216.145
  • 134.82.73.91

Attempts are starting. Block these addresses and check your web, proxy and WAF logs for them now.

Update: GreyNoise has since downgraded its classifications and currently lists no block candidates. See the 15:30 entry.

18 Nov 2026

Tenable ships its first Java4Shell plugins

Tenable has released its first Nessus plugins for CVE-2026-114938: plugin 382091 (Oracle Java SE November 2026 Critical Security Patch Update, labelled Java4Shell) and plugin 382045 (Amazon Corretto 17 before 17.0.21.1.2). Checks for the Amazon Linux 2 and Amazon Linux 2023 advisories have since shipped (see the 16:18 entry).

Both are local checks, so they need credentialed scans or Nessus Agents; there is no remote network check yet. They look at the installed Java version only, not whether the host CPU supports AVX-512 VBMI, and they do not yet cover Temurin, Microsoft, Zulu or distribution packages. A clean scan is not proof you are safe: runtimes bundled inside products will often be missed.

18 Nov 2026

Java4Shell goes global

Coverage has spread well beyond the security press this morning, with French, Spanish, Turkish and Japanese outlets all running the story. The Hacker News is leading on CISA's call for organisations to patch immediately.

Turkish outlet DonanımHaber reports that the bug was found using an unreleased OpenAI "GPT-6 Cyber" model.

18 Nov 2026

Ubuntu publishes its CVE page: every OpenJDK package still "Needs evaluation"

Ubuntu has now published its page for CVE-2026-114938. Every openjdk-17, openjdk-21 and openjdk-25 package from 18.04 to 26.10 is marked "Needs evaluation", and no fixed versions are listed yet.

Ubuntu initially rated the issue Medium priority; it has since raised it to High (see the 14:06 entry). As with Debian, apt upgrade will not fix this today: use -XX:-UseBASE64Intrinsics or a fixed vendor build until patched packages arrive.

18 Nov 2026

Hosting platforms start applying the mitigation for customers

Clever Cloud says its teams worked overnight to apply the Java4Shell mitigation to every Java application its platform launches, so no action is needed for those. Customers who start the JVM themselves still need to add -XX:-UseBASE64Intrinsics and redeploy.

Expect other platform-as-a-service and managed hosting providers to follow. If you run Java on a managed platform, ask your provider whether the flag or a fixed runtime has been applied, and whether that covers JVMs you launch yourself rather than through the platform.

18 Nov 2026

Debian stable and Ubuntu packages are not fixed yet

The Debian security tracker still marks every OpenJDK package in its stable releases as vulnerable, including the latest security-channel builds: openjdk-17 in bookworm, and openjdk-21 and openjdk-25 in trixie. Fixed packages (17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1) have so far landed only in unstable. Ubuntu has not yet published a page for the CVE.

If you rely on distribution OpenJDK packages, running apt upgrade will not fix this today. Use the -XX:-UseBASE64Intrinsics flag, or a vendor build that already contains the fix, until patched packages arrive.

18 Nov 2026

Red Hat rates Java4Shell Critical and lists likely vulnerable cloud instances

Red Hat has published security bulletin RHSB-2026-018, rating Java4Shell Critical. Affected products include RHEL 8, 9 and 10, Red Hat build of OpenJDK 17, 21 and 25, and anything that pulls from RHEL channels, including RHEL CoreOS, UBI-based containers, OpenShift, OpenStack and Virtualization. Red Hat says it is expediting fixes, but no errata are out yet. In the meantime it recommends -XX:-UseBASE64Intrinsics, to be removed once the permanent fix is applied.

The bulletin also lists cloud instance families likely to have AVX-512 VBMI, which is useful for prioritising:

AWSC6i, M6i, R6i, C7i, M7i, R7a
Google CloudC3, C3D, C4, C4D, N4, N4D, M3, M4
AzureDsv5, Dsv6, Dasv6, Dasv7 and related D-series v5 to v7

A quick check on any Linux host: grep -o avx512vbmi /proc/cpuinfo | head -1. Any output means the CPU meets the hardware condition.

18 Nov 2026

Watch: Calif demonstrates Java4Shell RCE against Keycloak, Jira, Confluence and more

Calif has published a short video showing Java4Shell remote code execution against real products, including Keycloak, Jira, Confluence, Kafka and Elasticsearch. Calif is still withholding the exploit code itself, but the demos make clear these are working attacks against widely deployed software, not theoretical memory corruption.

If any of these run on an affected JDK and an AVX-512 VBMI host in your estate, treat them as the top of the patching queue. Source: Calif on YouTube.

18 Nov 2026

Scanner coverage: Qualys detections live, Tenable plugins in the pipeline

Qualys has released three detections in VULNSIGS-2.6.747-3: QID 389494 (OpenJDK Java4Shell), QID 389610 (Oracle Java SE November 2026 Critical Patch Update) and QID 389608 (Amazon Corretto 17, 21, 25 and 27). Distribution-specific QIDs will follow as Linux vendors publish advisories.

Tenable has classed CVE-2026-114938 as a Vulnerability of Interest. Plugins will appear on the CVE page as they are released; in the meantime, the Java Visibility and Exposures report and the Explore > Software view will list Java installs to compare against the affected versions.

One caution: scanners see installed packages. Runtimes bundled inside products and appliances often do not show up as a separate Java install, and an operating system update will not patch them. Scanners also will not tell you whether the host CPU has AVX-512 VBMI.

18 Nov 2026

What to hunt for in your logs

Detection guidance from Upwind, Qualys and CISA points to a small set of signals worth hunting for now:

  • Request shape: a Base64-alphabet token of 32 or more characters that ends in an equals sign and whose length is not a multiple of four. Start with Authorization headers.
  • Application logs: bursts of IllegalArgumentException thrown from java.util.Base64$Decoder.
  • Crashes: unexplained hs_err_pid*.log files, or bursts of JVM restarts on internet-facing Java services. Failed exploit attempts often crash the JVM, and attackers can simply retry.
  • Process behaviour: Java processes starting a shell or opening new outbound connections.
  • Unknown runtimes: Java running on hosts your inventory does not account for.

A hit does not prove compromise, and no hits does not prove you are safe. Patch first, hunt second.

18 Nov 2026

Lab exploit code and detection tooling appearing on GitHub

Calif is withholding its product-specific exploit chains until organisations have had time to patch, but the gap is closing. Overnight, a number of Java4Shell repositories have appeared on GitHub, including reproduction labs, read-only exposure checkers and at least one repository claiming a working lab RCE chain against Temurin 21.0.13 on an AMD Zen 4 host. We have not verified any of them.

Separately, Kevin Breen of Immersive said yesterday evening that he has a working application-specific exploit, naming Apache Tomcat Basic authentication and the java-jwt library as pre-login paths. It has not been released.

As with every major disclosure, expect fake PoCs that drop backdoors or stealers on whoever runs them. Do not clone or execute unverified exploit code on anything you care about. Calif's own trigger PoC is bounded and only tells you whether a JDK and CPU combination reproduces the bug.

18 Nov 2026

Cannot patch today? Disable the Base64 intrinsic

Calif identified two JVM startup options that stop the vulnerable code from running. Neither Oracle nor the OpenJDK Vulnerability Group mentions them, and neither replaces the patch.

Preferred

-XX:-UseBASE64Intrinsics turns off the hand-written fast decoder and falls back to the standard Java one. Upwind found it stopped the overflow on every affected version they tested, and it is safe on any architecture. Services that decode a lot of Base64 may slow down, so test first.

Alternative, x86-64 only

-XX:UseAVX=2 disables AVX-512 entirely, so the performance cost is wider. Java on ARM will not start with this option.

Both flags only take effect after a restart. For containers, recreate them so the flag reaches the running process, then confirm it on the live JVM (for example with jcmd <pid> VM.flags) rather than trusting the deployment config.

18 Nov 2026

Fixed builds: what is out and what is still coming

Oracle shipped fixed builds in its November 2026 Critical Security Patch Update. The fixed builds end in .1:

Java lineVulnerable Oracle buildFixed Oracle build
8 Enterprise Performance Pack8u511b33-perf8u513-perf
1717.0.21.0.317.0.21.1
2121.0.13.0.321.0.13.1
2525.0.5.0.325.0.5.1
2727.0.1.0.327.0.1.1

Amazon has released Corretto 17.0.21.1.2 with the fix, and GraalVM fixes are listed in Oracle's advisory. Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine and Red Hat OpenJDK all carry the same vulnerable code and are publishing on their own schedules. Upwind reproduced the bug on Temurin 17.0.21, 21.0.13 and 25.0.5, so do not assume the latest non-Oracle build is safe until your vendor says so.

After upgrading, restart services and rebuild container images. An upgraded package with an old JVM still running is still vulnerable.

18 Nov 2026

Which applications are exposed

Base64 is everywhere in Java: login headers, tokens and file uploads. That is why the vulnerable code often runs before authentication. In Calif's testing, using default configurations on affected JDKs and CPUs:

RCE before login

Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, PingFederate

RCE after login

Apache Kafka broker, Apache Solr, Elasticsearch, Gerrit, Spinnaker

Calif also reached code execution in sample apps built on Apache Struts and Spring Boot. Upwind's lab found pre-auth paths through Spring Security, Tomcat and Jetty 12 Basic authentication, and Auth0's java-jwt library. These lists are not exhaustive.

Clients are exposed too. A client-side exploit from researcher samczsun compromises a Java program when it connects over TLS to a malicious server, even if that program offers no service of its own. Build agents, integration jobs and anything making outbound HTTPS calls need patching as well.

18 Nov 2026

Are you exposed? Three conditions, and one of them can change under you

A system is exploitable when all three of these are true:

  1. An affected JVM. OpenJDK-based builds from 17.0.6 onwards, including Java 21, 25 and 27, plus Oracle's 8u511b33-perf build. Standard Java 8, Java 11 and 17.0.0 to 17.0.5 are not affected. Runtimes bundled inside products count.
  2. An x86-64 CPU with AVX-512 VBMI. Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids; AMD EPYC and Ryzen Zen 4 and newer. On AWS that includes c6i, m6i, c7i, c7a and m7a. ARM64 is not affected.
  3. Untrusted Base64 reaching the JDK decoder (Base64.getDecoder() or getUrlDecoder()) once it has been JIT-compiled, which happens on any busy service.

To check the CPU on Linux, all four flags must appear:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

Use the CPU check to prioritise, not to close tickets. The same container image can be exposed on one node and safe on another, and a resize, migration or autoscaling event can move a workload onto affected hardware without anyone noticing.

18 Nov 2026

BBC brings Java4Shell to UK mainstream news; no evidence links this week's outages

The BBC reported the AI-found Java flaw overnight, describing Java as used by banks, hospitals and governments as well as the world's largest companies. Computer scientist Professor Toby Walsh called it "such an unlikely and serious flaw" given that Java is designed to manage memory safely.

The coverage landed in the middle of a run of major outages this week, including Microsoft, Apple services, US flights and the NSA's internal network. There is no evidence linking any of them to Java4Shell: the NSA did not say whether its outage was related, and US Secretary of State Marco Rubio said there was "zero evidence" the incidents were connected.

Evening17 Nov 2026

CISA urges immediate patching

CISA has published an alert, Critical Java Vulnerability Requires Immediate Patching, warning that crafted input can crash the JVM as well as enable code execution. It recommends validating Base64 input and enforcing size limits at the application boundary, and monitoring for rogue runtimes, unexpected JVM crashes and suspicious Java processes.

Note that size limits alone will not stop this bug: the malformed input that triggers it is very short.

17 Nov 2026

Chainguard says it found Java4Shell independently days before disclosure

Chainguard chief executive Dan Lorenc said on X that his team "found and reported java4shell independently Friday night while scanning an open source Java project", on 13 November. Lorenc said Calif had beaten them to it by a few weeks. Chainguard has since published remediation tooling that inventories JDK packages in its container images from their signed SBOMs.

Two separate teams finding the same bug within days is the pattern we saw with PHP2Shell too. It is a strong sign that well-resourced attackers using the same AI-assisted methods can find bugs like this as well.

17 Nov 2026

Patches and full disclosure: Oracle CSPU, OpenJDK advisory and Calif write-up

At 13:00 Pacific, Oracle released its November 2026 Critical Security Patch Update, the OpenJDK Vulnerability Group published its advisory, and Calif published its technical write-up, Java4Shell: Write once, RCE everywhere. Java4Shell is one of 11 Java SE fixes in the update. Oracle credits Quang Luong of Calif and Albert Yang.

Calif says Luong found the bug while auditing HotSpot with an AI coding assistant, focusing on the JIT compiler, intrinsics and widely used APIs. Discovery took about an hour, the first working exploit about two more, and the total AI cost was under $200. It is the same team behind PHP2Shell last month.

Earlier17 Nov 2026

Details leak ahead of the patch

Oracle's pre-release announcement flagged 11 Java SE vulnerabilities, each remotely exploitable, without naming them. heise reported an unconfirmed Base64 decoder flaw affecting OpenJDK 17.0.6 onwards under the name Java4Shell.

Calif then confirmed on X that it had found and reported the flaw and that details had leaked before a fix was available. Upwind flagged the issue early and reproduced it on an AWS c6i instance before the official advisory landed.

16 Nov 2026

The fix lands quietly in OpenJDK as "Base64 optimization improvements"

The fix went into OpenJDK's public repository the day before disclosure, as commit 5177a70b with the bland title "8393212: Base64 optimization improvements". It adds four lines to the x86-64 stub generator, sending inputs shorter than four characters down the safe path, and was co-authored by Albert Yang, who Oracle credits alongside Calif.

Landing a security fix in public under an innocuous name before the advisory is common practice, but anyone diffing the repository could spot it. Together with Oracle's pre-announcement, it helps explain how details leaked ahead of the coordinated release.

Background17 Jan 2023

Where it started: OpenJDK 17.0.6 ships the vulnerable decoder

The vulnerable code reached Java 17 users on 17 January 2023, when OpenJDK 17.0.6 shipped the AVX-512 Base64 decoding intrinsic. It was the first Java 17 release with the flaw, which is why 17.0.0 to 17.0.5 are not affected, and the same code has been carried into Java 21, 25 and 27 since.

That means Java4Shell sat in production runtimes for almost four years before Calif found it. Faster Base64 decoding on newer Intel and AMD server chips was a genuine performance win, and nobody spotted the edge case in its hand-written assembly. The date comes from GreyNoise's Java4Shell timeline.

Why speed matters: one hour to find, two hours to exploit

Calif found Java4Shell in about an hour with AI assistance and had a working exploit two hours later, for under $200. The root cause and technique are public. Withholding the product-specific chains buys defenders time, but anyone with the same tools can rebuild them, and lab exploit code is already circulating.

Java has a history here: CISA's Known Exploited Vulnerabilities catalog lists 13 Oracle Java SE and JRE flaws, six of them used in ransomware campaigns. Treat the absence of in-the-wild reports as a head start, not a reason to wait.

Java4Shell frequently asked questions

Is Java4Shell the same as Java2Shell?

Yes. Java2Shell is an alternative name some people use for Java4Shell. Both refer to CVE-2026-114938, the OpenJDK Base64 decoder memory corruption flaw disclosed by Calif on 17 November 2026. JavaBleed is the name Calif gave to the related heap memory disclosure technique.

What is Java4Shell?

Java4Shell is the name for CVE-2026-114938, a critical memory corruption vulnerability in the OpenJDK Base64 decoder. On x86-64 CPUs with AVX-512 VBMI, a short malformed Base64 string makes the hardware-accelerated decoder write 62 bytes past the end of a heap buffer. Researchers at Calif turned this into heap memory disclosure (JavaBleed) and unauthenticated remote code execution. It is rated CVSS 9.2 on v4.0 and 8.1 on v3.1.

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

OpenJDK-based builds from 17.0.6 onwards are affected, including Java 17, 21, 25 and 27, along with Oracle Java SE 8 Enterprise Performance Pack build 8u511b33-perf. Standard Java 8, Java 11 and Java 17.0.0 to 17.0.5 are not affected. All major distributions carry the vulnerable code, including Oracle, Eclipse Temurin, Amazon Corretto, Microsoft, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat and GraalVM.

Which versions fix Java4Shell?

Oracle fixed builds are 8u513-perf, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, released on 17 November 2026. Amazon Corretto 17.0.21.1.2, 21.0.13.1.2 and 25.0.5.1.2, Azul Zulu 17.0.21.1, 21.0.13.1 and 25.0.5.1, Microsoft Build of OpenJDK 17.0.21.1, 21.0.13.1 and 25.0.5.1, and BellSoft Liberica 21.0.13.1 include the fix. As of the afternoon of 18 November 2026, Eclipse Temurin, Debian, Ubuntu and Red Hat had not yet shipped fixed packages, and Keycloak had no fixed container image, so use -XX:-UseBASE64Intrinsics until they do. Restart every JVM and rebuild container images after upgrading.

Am I affected if my servers do not have AVX-512?

Not today. The bug only triggers on x86-64 CPUs with AVX-512 VBMI, such as Intel Xeon Ice Lake and newer or AMD Zen 4 and newer. ARM64 is not affected. However, workloads can move onto affected hardware after a cloud resize, migration or autoscaling event, so you should still patch.

Is Java4Shell being exploited in the wild?

Exploit attempts have been seen. As of 18 November 2026, GreyNoise has recorded Java4Shell-shaped requests from a small number of IP addresses, with no confirmed successful compromise, and the CVE is not yet in the CISA Known Exploited Vulnerabilities catalog. The technique is public, a researcher has an unreleased working exploit, lab exploit code is appearing on GitHub, and Calif built its first exploit in about two hours. Assume exploitation is imminent.

How can I mitigate Java4Shell if I cannot patch immediately?

Start the JVM with -XX:-UseBASE64Intrinsics, which disables the vulnerable fast decoder and works on any architecture. -XX:UseAVX=2 also works but only on x86-64; ARM JVMs will fail to start with it. Both require a restart and neither replaces the patch. Move identity, build and collaboration consoles such as Keycloak, Jenkins and Confluence off the open internet until patched.

Which applications are affected by Java4Shell?

Calif demonstrated pre-authentication RCE in default configurations of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, and post-authentication RCE in Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Sample Apache Struts and Spring Boot apps were also exploitable, as were Java clients connecting to malicious TLS servers. The list is not exhaustive.

How do I check if my server is vulnerable to Java4Shell?

Check three things. First, the Java version with java -version: OpenJDK-based builds from 17.0.6 onwards (17, 21, 25 and 27) without the November 2026 fix are affected. Second, the CPU: on Linux, run grep -o avx512vbmi /proc/cpuinfo; any output means the hardware condition is met. Third, whether the application decodes untrusted Base64, which most web, identity and CI/CD services do. Remember runtimes bundled inside products and containers.

Is Java4Shell as bad as Log4Shell?

Both are unauthenticated remote code execution flaws in ubiquitous Java components, but Java4Shell is harder to exploit at scale. Log4Shell worked on almost any vulnerable application on any CPU with a single string. Java4Shell needs an affected JDK, an x86-64 CPU with AVX-512 VBMI and an exploit chain tailored to each application, so researchers expect targeted rather than mass exploitation. High-value systems such as Keycloak, Jenkins, Jira and Confluence remain at serious risk.

Need help responding to Java4Shell?

Precursor's CREST-accredited SOC monitors for active exploitation 24/7. If you need help finding exposed Java services, prioritising patching or investigating a suspicious crash, we can help.