On this page · 12 sections
- What is confirmed, and by whom
- Affected versions and the fixed builds
- Who is actually exposed
- Detection: find every runtime first
- If you cannot patch today: the interim flag
- Patch plan: the order to work in
- US and UK: what the deadlines mean
- The licensing catch with Oracle JDK 21
- Worked example: a 140-JVM SaaS estate
- Choose your route
- How eCorpIT can help
- References
Summary. Oracle and the OpenJDK project fixed CVE-2026-114938, which its finders at Calif call Java4Shell, in the November 2026 Critical Security Patch Update released on 17 November 2026. It is heap memory corruption in the HotSpot JVM's AVX-512 Base64 decoder, so it can only be reached on x86-64 CPUs with AVX-512 VBMI (Intel Xeon from Ice Lake, AMD Zen 4 and later); ARM64 is not affected. Oracle scores it 8.1 under CVSS 3.1 and Calif scores it 9.2 under CVSS 4.0. OpenJDK 17 (from 17.0.6), 21, 25 and 27 are affected; standard Java 8 and 11 are not. The fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and Temurin, Corretto, Microsoft, Zulu, Red Hat, Debian and Ubuntu have all shipped matching builds. Java 26 and other non-LTS lines get no fix. CISA urged immediate patching on 17 November, and the CVE was still not in its Known Exploited Vulnerabilities (KEV) catalogue in the 20 November edition. If you cannot patch today, restart affected JVMs with -XX:-UseBASE64Intrinsics. UK organisations working to Cyber Essentials have until 1 December 2026.
About this article. This guide is for CISOs, platform leads and Java engineering managers in the US and UK. On 21 November 2026 we checked it against Oracle's advisory, release notes and security baseline, the OpenJDK advisory, NVD and the CVE record, CISA's alert, KEV feed and BOD 26-04, each distributor's changelog, release notes, package API or security tracker, Calif's disclosure and the NCSC's Cyber Essentials requirements. We give no exploit detail beyond what those sources publish. This is general information, not legal advice, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.
Calif also disclosed PHP2Shell, the flaw attackers used to get into Check Point gateways, covered in our PHP2Shell and CVE-2026-123039 guide.
What is confirmed, and by whom
The rows draw on Oracle and NVD, the OpenJDK advisory, CISA's enrichment, Calif, CISA's alert and KEV feed, and Azul.
| Fact | Source | Status |
|---|---|---|
| Fixed in the November 2026 Critical Security Patch Update, Rev 1, 17 November 2026; 655 new patches, 11 for Java SE | Oracle advisory | Confirmed |
| Component Compiler; CVSS 3.1 base 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H; remotely exploitable without authentication | Oracle risk matrix, NVD | Confirmed |
| OpenJDK 17, 21, 25 and 27 affected; 8 and 11 not; component hotspot/compiler | OpenJDK advisory | Confirmed |
| Heap-based buffer overflow (CWE-122); exploitation none, not automatable, total technical impact | CISA enrichment on the CVE record | Confirmed |
| Name Java4Shell; Base64 decoder memory corruption; needs x86-64 with AVX-512 VBMI; OpenJDK 17.0.6 and later | Calif disclosure | Researcher |
| CVSS 4.0 score 9.2 | Calif disclosure | Researcher rating |
| CISA alert urging immediate patching, 17 November 2026 | CISA | Confirmed |
| Not in KEV catalogue version 2026.11.20 (1,790 entries) | CISA KEV feed | Confirmed on 21 November |
| No exploitation in the wild reported as of the evening of 17 November | Azul | Vendor statement |
Oracle credits the report to Albert Yang and to Quang Luong of Calif.io. Calif's write-up says a user first hit the crash and reported it on an Adoptium support issue in June 2026, that a fix was proposed in OpenJDK in September and closed without being merged, and that Calif reported exploitability to Oracle on 24 October. Azul says it is not a zero-day, because it went through the OpenJDK process and the fix shipped in the scheduled update.
Scores differ by distributor. Red Hat rates the flaw Critical with its own CVSS 3.0 score of 9.8, so scanners may show different numbers for the same CVE.
The next Oracle security dates are 15 December 2026 (monthly CSPU) and 19 January 2027 (quarterly CPU). Oracle's release notes for 21.0.13.1 say not to use that build after 19 January 2027, so plan a second roll-out in January either way.
Affected versions and the fixed builds
Oracle's matrix lists the last supported versions that are affected. Treat earlier versions in the same lines as affected too, from 17.0.6 onward according to Calif and Red Hat. The table draws on Oracle's advisory, release notes and security baseline file.
| Product line | Oracle lists as affected | Fixed build (17 November 2026) | Note |
|---|---|---|---|
| Oracle Java SE 27 | 27.0.1.0.3 | 27.0.1.1 | Non-LTS feature release |
| Oracle Java SE 25 | 25.0.5.0.3 | 25.0.5.1 | LTS |
| Oracle Java SE 21 | 21.0.13.0.3 | 21.0.13.1 (21.0.13.1+4) | LTS; OTN licence since 21.0.13 |
| Oracle Java SE 17 | 17.0.21.0.3 | 17.0.21.1 | LTS |
| Oracle Java SE 8 Performance Pack | 8u511b33-perf | 8u513-perf | Subscription-only Enterprise Performance Pack |
| Oracle Java SE 8 and 11 (standard) | Not listed for this CVE | 8u513 and 11.0.33.1 | Fix other November CVEs, two of them scored 7.4 |
| Oracle GraalVM for JDK 21 | 21.0.13.0.3 | 21.0.13.1 | Built on JDK 21.0.13.1+4 |
| Oracle GraalVM for JDK 17 | 17.0.21.0.3 | 17.0.21.1 | November CSPU release |
| Oracle GraalVM Enterprise Edition | 21.3.20.0.3 | Through My Oracle Support | Patch availability document CPU435 |
Oracle's published security baseline file read 27.0.1.1, 25.0.5.1, 21.0.13.1, 17.0.21.1, 11.0.33.1 and 1.8.0_513 when we checked it on 21 November. Anything below those strings is behind on November's fixes.
One trap matters for scanners. The update digits do not change: 21.0.13 becomes 21.0.13.1, and 17.0.21 becomes 17.0.21.1. A rule that asks whether a runtime is at least 21.0.13 passes both the vulnerable and the fixed build. We described the same problem with Corretto's August patch in our Corretto version-detection gap piece. Match on all four fields.
OpenJDK distributions: release status on 21 November
The table draws on Adoptium's guidance, API and Docker Hub tags, Corretto's changelogs and Docker Hub tags, Azul's blog and public package API, Microsoft's release notes, Red Hat's security data, and the Debian and Ubuntu trackers.
| Distribution | Fixed builds | Status |
|---|---|---|
| Eclipse Temurin | 27.0.1.1+4, 25.0.5.1+2, 21.0.13.1+2, 17.0.21.1+2 | GA in the Adoptium API from 18 November; Docker Hub images such as 21.0.13.1_2 from 20 November |
| Amazon Corretto | 27.0.1.1.4, 25.0.5.1.2, 21.0.13.1.2, 17.0.21.1.2 | Released 17 November; Docker Hub tags keep the plain version, such as 21.0.13, so pull again and rebuild |
| Azul Zulu (Azul Core) | Public builds Zulu 27.30.201, 25.38.201, 21.54.201 and 17.70.201 (JDK 27.0.1.1, 25.0.5.1, 21.0.13.1, 17.0.21.1) | Released; Azul Prime is fixed in 26.08.110.0 and 26.02.510.0 and is also affected on Java 8 and 11 |
| Microsoft Build of OpenJDK | 25.0.5.1, 21.0.13.1, 17.0.21.1 | Listed in Microsoft's release notes against the 17 November advisory |
| Red Hat build of OpenJDK and RHEL | 25.0.5.1.2, 21.0.13.1.2, 17.0.21.1.2 packages | Errata for RHEL 8, 9 and 10 on 19 November; rated Critical; several Red Hat container images still listed as affected |
| Debian | 25.0.5.1+2, 21.0.13.1+2, 17.0.21.1+2 | Fixed in trixie (openjdk-21 and 25) and bookworm (openjdk-17, through Debian LTS); testing still vulnerable |
| Ubuntu | 27.0.1.1+4, 25.0.5.1+2, 21.0.13.1+2, 17.0.21.1+2 | Security notices on 18 November; Ubuntu 18.04 and 20.04 get fixes through Ubuntu Pro |
| BellSoft Liberica, SAP SapMachine | Not checked by us | Calif lists them as affected; check each vendor advisory |
Running Java 26 or another non-LTS line? There is no fix for you. The OpenJDK advisory covers only 8, 11, 17, 21, 25 and 27, Oracle's baseline file shows 26 as no longer updated (26.0.99), and Amazon Linux lists its Corretto 22, 23, 24 and 26 packages as no fix planned. Calif puts every OpenJDK release from 17.0.6 onward in range, which takes in those lines. Move those services to 25.0.5.1 or 27.0.1.1, or set the interim flag below until you can.
Who is actually exposed
Three things must all be true.
- The runtime is in range. OpenJDK-based Java 17.0.6 or later, 21, 25 or 27, from any vendor, below the 17 November build, plus the unpatched non-LTS lines. Oracle's Java 8 Performance Pack and Azul Prime on Java 8 and 11 are also in range. Standard Java 8 and 11 are not.
- The CPU has AVX-512 VBMI and the JVM uses it. Calif names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen from Zen 4. Azul notes that AVX-512 is on most current-generation x86 server processors and the cloud instances built on them. AWS Graviton, Ampere and other ARM64 hosts are not affected.
- Untrusted data reaches Java's Base64 decoder. That is common. Base64 carries HTTP Basic credentials, JWT segments, SAML assertions, file uploads and message payloads, so the vulnerable path can run before login. Oracle's note says the flaw is exploited by supplying data to the affected APIs, for example through a web service.
Calif reports pre-authentication remote code execution against Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate in default configurations, and post-authentication against Kafka brokers, Solr, Elasticsearch, Gerrit and Spinnaker. It also reports a client-side path, where a Java program that connects over TLS to a hostile server can be compromised. Calif is withholding its product-specific chains and says each target needs its own approach. That buys time, not safety. Red Hat notes that exploitation can also crash the service, so availability is at risk even where code execution is hard.
Detection: find every runtime first
CISA's alert warns that JDKs bundled inside third-party products, container images and appliances often do not show up as separate inventory items. Start there.
Run these read-only checks on each Linux host or inside each running container:
# 1. Which Java is on the path, and its full version string
java -version 2>&1
# 2. Does the CPU expose the instructions the vulnerable code needs?
# All four flags must print for the host to be in scope.
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
# 3. Is the JVM using AVX-512 and the Base64 intrinsic?
java -XX:+PrintFlagsFinal -version 2>/dev/null | grep -E ' (UseAVX|UseBASE64Intrinsics) '
# 4. The java on the path is often not the one a service runs. Check live JVMs.
jcmd -l
jcmd <pid> VM.version
jcmd <pid> VM.flags -all | grep -E ' (UseAVX|UseBASE64Intrinsics) '
The CPU check is Calif's own. A host is taking the vulnerable path when the version is in range, all four CPU flags print, UseAVX reports 3 and UseBASE64Intrinsics is true. Oracle documents UseAVX as defaulting to the highest level the CPU supports, and VM.flags needs -all to print values the JVM chose for itself. On Windows servers, check the CPU model against the list above and read the runtime version from each service's install directory.
Then widen the search:
- Bundled runtimes. Jira, Confluence, Jenkins, Keycloak, Artifactory, Elasticsearch and many vendor appliances ship their own JDK under the install directory. The OS package manager will not update these, so you wait for each vendor or swap the runtime where the vendor supports it. On 21 November Red Hat still listed its Keycloak, AMQ Broker, JBoss EAP and streams for Apache Kafka images as affected.
- Container images. Search your registry and SBOMs for base images built on Java 17, 21, 25 or 27, including
eclipse-temurin,amazoncorretto, Microsoft and Red Hat images. A running container keeps the old JVM until you rebuild and redeploy.
- Managed platforms. Check whether your PaaS, serverless runtime or managed Kafka and search services have published their own status; do not assume a provider has rolled the JVM for you.
- Crash evidence. Look for new
hs_err_pid*.logfiles, unexpected JVM restarts and bursts ofIllegalArgumentExceptionfromjava.util.Base64on internet-facing services since mid-November. Calif notes that Java rejects the malformed input only after the out-of-bounds write, and CISA lists unexpected JVM crashes and rogue runtimes as signals worth investigating.
If you cannot patch today: the interim flag
Calif documents two JVM options that remove the vulnerable code path. Adoptium recommends the first as its interim mitigation, and Azul repeats both.
| Option | What it does | Caveats |
|---|---|---|
| -XX:-UseBASE64Intrinsics | Turns off the hardware-accelerated Base64 routine, so decoding runs in ordinary Java code | Recommended interim fix; may slow Base64-heavy workloads; needs a JVM restart |
| -XX:UseAVX=2 | Stops the JVM using AVX-512 at all | Broader performance cost; x86-64 only, because OpenJDK on ARM does not recognise the option and will fail to start |
Oracle's java documentation shows the JAVA_TOOL_OPTIONS environment variable being used to add options without editing a start-up script. Set JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics in the service environment, container spec or systemd unit, then restart. If the variable already holds options, append the flag rather than replacing them. Confirm it took effect with the jcmd check above. The flag does not replace the update: November's release also fixes ten other Java SE CVEs, scored up to 7.5.
CISA adds compensating controls for systems you cannot touch yet: validate and size-limit Base64 input at the application boundary, and reduce unauthenticated access. Azul cites Wiz's view that web application firewall rules are unlikely to cover every path, and Calif notes that proxy request buffering defeats only some of its techniques. Treat both as extra layers.
Patch plan: the order to work in
| Wave | Systems | Target | Why |
|---|---|---|---|
| 0 (today) | Set -XX:-UseBASE64Intrinsics on every in-scope internet-facing JVM you cannot update this week | Within 24 hours | Removes the code path while change control runs |
| 1 | Internet-facing identity, CI/CD and collaboration: Keycloak, PingFederate, Jenkins, Artifactory, Jira, Confluence, API gateways written in Java | By 25 November 2026 | Demonstrated pre-auth targets; they hold tokens and build credentials |
| 2 | Other internet-facing Java services on AVX-512 x86 hosts, including Spring Boot APIs | By 28 November 2026 | Same exposure class, less blast radius |
| 3 | Internal services that decode partner, queue or user data; Kafka, Solr and Elasticsearch clusters | By 1 December 2026 | Post-auth targets; meets the UK 14-day rule |
| 4 | Desktop and batch Java clients, build agents, developer JDKs | By 15 December 2026 | Client-side TLS path; next Oracle CSPU lands the same day |
The order follows CISA's advice to put internet-facing systems first and Azul's ranking of identity, build and collaboration systems ahead of the rest. If you certify under Cyber Essentials, wave 4 cannot wait for 15 December. Every in-scope system needs the November update by 1 December, ARM hosts and Java 8 and 11 included, because the same release fixes CVE-2026-114939 and CVE-2026-114940, both scored 7.4, on every Java line.
Verify each wave: confirm the four-field version on every restarted process, re-run the CPU and flag cross-check to catch stragglers, and rebuild images instead of re-pulling tags. Then plan the 19 January 2027 quarterly update, because Oracle's 21.0.13.1 notes say that build should not be used after that date.
US and UK: what the deadlines mean
United States. CISA's 17 November alert asks organisations to inventory Java, including bundled and containerised runtimes, patch internet-facing systems first, apply compensating controls where they cannot patch yet, and watch for rogue runtimes and unexpected JVM crashes. For federal civilian agencies, BOD 26-04, issued on 10 June 2026, replaced BOD 22-01 and sets remediation deadlines from public exposure, KEV status, and CISA's automatable and technical-impact ratings. CISA's enrichment rates this CVE not automatable with total technical impact. While it stays out of KEV, the directive's table maps that to 14 days for publicly exposed assets and to the next scheduled upgrade for internal ones. If CISA adds it to KEV, exposed assets drop to 3 days plus forensic triage. KEV deadlines apply now; the full table becomes mandatory 180 days after issue, on 7 December 2026. BOD 26-04 binds federal civilian agencies, not private companies.
United Kingdom. The NCSC's Cyber Essentials requirements (v3.3, April 2026) say updates that fix vulnerabilities the vendor calls critical or high risk, or that score CVSS v3 7 or above, must be installed within 14 days of release. An 8.1 released on 17 November lands that deadline on 1 December 2026 (17 November plus 14 days). The same document defines software to include interpreters and libraries, so on our reading a JDK bundled inside a vendor product is in scope, and it warns that an update fixing several issues must go in within 14 days if any one of them is high risk. Our Cyber Essentials Danzell guide explains why a missed 14-day patch now fails the assessment outright.
The licensing catch with Oracle JDK 21
Oracle's release notes for JDK 21.0.13.1 restate that 21.0.13 was the first JDK 21 update under the Oracle Technology Network licence rather than the no-fee terms. If you install Oracle's own 21.0.13.1 binary in production without a Java SE subscription, the security fix may create a licence question. Our Oracle JDK 21 OTN licence audit guide covers the options. The practical answer for many teams is to take the same OpenJDK fix from Temurin, Corretto, Microsoft or Zulu, under that distributor's own terms.
Worked example: a 140-JVM SaaS estate
Take a US and UK SaaS company with 140 production JVMs on AWS: 60 Spring Boot services on Temurin 21 in containers on m7i instances (4th Generation Intel Xeon, code-named Sapphire Rapids, so AVX-512 VBMI is present), 30 services on Corretto 17 on Graviton (ARM64), a self-hosted Jenkins controller with 20 x86 agents, one Keycloak instance for customer login, and 28 Kafka brokers on x86. That is 60 + 30 + 1 + 20 + 1 + 28 = 140.
- Scope. The 30 Graviton services are out of scope for this CVE. That leaves 110 JVMs.
- Wave 0. Add
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsicsto the Keycloak and Jenkins controller deployments and roll them, about 1 hour of platform time.
- Wave 1. Rebuild the Keycloak, Jenkins controller and Jenkins agent images on 21.0.13.1-based images, test login and a pipeline run, and deploy. Allow 6 engineer-hours, including rollback rehearsal.
- Wave 2. The 60 Spring Boot services share three base images. Bump the base once, let CI rebuild 60 services, run smoke tests and roll in two batches. At 10 minutes of review per service, 60 × 10 = 600 minutes, or 10 hours, plus 4 hours of coordination: 14 engineer-hours.
- Wave 3. Roll the 28 Kafka brokers one at a time on the new runtime, about 8 hours of mostly waiting.
- Graviton. The 30 Corretto 17 services are not exposed to Java4Shell, but they still need 17.0.21.1.2 for the other November CVEs. Under Cyber Essentials that is also due by 1 December; otherwise it can go in the normal cycle.
That is 1 + 6 + 14 + 8 = 29 engineer-hours, roughly 30, to close the exposure before 1 December, against a quarterly cycle that would have left it open until 19 January. These figures are planning assumptions, not measurements; your test suite length decides most of the time.
Choose your route
| Choose this | If |
|---|---|
| Patch to the 17 November build now | You control the runtime (your own images, packages or install), and you can restart within the week |
| Set -XX:-UseBASE64Intrinsics first, then patch | The service is internet-facing and change control or vendor testing will take more than a day |
| Ask the vendor and set the flag where supported | The JDK is bundled inside a product such as Jira, Artifactory or an appliance |
| Swap Oracle JDK 21 for an OpenJDK build | You run Oracle JDK 21 in production without a Java SE subscription |
| Patch in the normal cycle | The host is ARM64, or x86 without AVX-512 VBMI, only the other November CVEs apply, and you are not bound by the Cyber Essentials 14-day rule |
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our cybersecurity services team can inventory Java runtimes across hosts and containers, roll out the interim JVM flag and add four-field version checks to your CI. Talk to us at /contact-us/.
Last updated: 21 November 2026.