Vulnerability · patch available

Java4Shell CVE-2026-114938Crafted Base64 data can take down or take over Java servers

On November 17, 2026, the security company Calif disclosed a flaw in the OpenJDK Base64 decoder; Oracle and the OpenJDK project released updates the same evening. On servers with certain Intel and AMD processors, the decoder writes beyond the end of its memory buffer when it processes crafted input. According to its own claims, Calif used this to achieve code execution without authentication in Jira, Confluence, Jenkins, Keycloak, Artifactory and PingFederate. Successful exploitation has not been confirmed so far, but initial attempts have been recorded.

  • CVSS 9.2 (Calif) · 8.1 (Oracle)
  • Java 17.0.6 to 27 on x86-64 with AVX-512 VBMI
  • Fix in the Oracle update of November 17, 2026
  • Workaround: -XX:-UseBASE64Intrinsics

At a glance

What happened and what it means for you

Java4Shell is not in a library but in the Java runtime itself. On modern x86 processors, the HotSpot JVM speeds up Base64 decoding with special instructions, and it is precisely this fast path that miscalculates with certain inputs. Base64 is used in logins, tokens and uploads, so the potential reach is correspondingly large. Three questions determine whether you are affected: Java version, processor and reachable inputs. [1][2][3]

  1. The runtime is affected, not your code. Any application that decodes externally supplied Base64 data with java.util.Base64 on a vulnerable JVM can be open to attack, even if the application itself is free of errors.
  2. Only on certain processors. The faulty path only runs on x86-64 processors with AVX-512 VBMI, such as Intel Xeon of the Ice Lake to Granite Rapids generations and AMD from Zen 4 onward. ARM servers are not affected.
  3. Well-known applications are vulnerable. According to its own tests, Calif executed code in default configurations: before authentication in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and after authentication in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.
  4. Authorities are pressing for action. CISA, the Canadian Centre for Cyber Security, CERT-EU, Switzerland’s Federal Office for Cybersecurity (BACS) and Germany’s Federal Office for Information Security (BSI) issued warnings on November 17 and 18. CISA and CERT-EU advise updating internet-facing systems first.
  5. The fix is a Java update, often hidden inside the product. Oracle has released patched versions, and other vendors are following suit. If an application ships with its own Java runtime, you need the vendor’s update or, until then, the workaround.

What is established

  • Calif disclosed the flaw on November 17; Oracle and the OpenJDK project released updates and an advisory the same evening.
  • Affected are OpenJDK 17.0.6 and later as well as the 21, 25 and 27 lines, and all distributions based on the HotSpot JVM.
  • The fix, JDK-8393212, comprises four lines. Until it is installed, two JVM options disable the vulnerable path.
  • Crashing a JVM is considered easy. VulnCheck has been offering its customers a full exploit since November 18.
  • On November 18, GreyNoise recorded the first requests that look like Java4Shell attempts, so far without any successful intrusion into its sensors.

What remains unclear

  • When all vendors will deliver patched builds; Eclipse Temurin (except Java 27 for Linux x64), Microsoft, Red Hat, Ubuntu and SUSE still had no fix on November 18.
  • Which applications beyond Calif’s list are vulnerable; the list is explicitly incomplete.
  • When Calif will publish the application-specific exploit chains.
  • Whether attackers are already deliberately exploiting the flaw; this has not been confirmed so far.
  • How Atlassian, Elastic, JFrog, Ping Identity and other vendors will respond; by November 18, only Keycloak had published a recommendation.
Attack chain

How a Base64 string turns into code execution

Calif describes these steps in its disclosure. For now, Calif is withholding how the chain reaches its goal in individual applications, so that operators have time to patch. [1][6]

  1. According to Calif

    Crafted input

    Attackers send a manipulated Base64 string to a point where the application decodes it, for example in the credentials of a request, in a token or during a file upload.

  2. According to Calif

    Fast path

    Only once the C2 JIT compiler has optimized the decoding does a processor routine using AVX-512 VBMI take over. To achieve this, Calif deliberately warms up the decoder with requests.

  3. According to Calif

    Writing past the end

    With certain endings that contain padding characters, the routine miscalculates the remaining length and writes 64 bytes instead of fewer, up to 63 of them past the end of the buffer. Just 64 “A” characters and one “=” are enough to trigger this; on Java 17, it takes 128 characters.

  4. According to Calif · details withheld

    Shaping memory

    With further requests, attackers arrange the memory so that the overflow hits specific data. A read variant that Calif calls “JavaBleed” reads out memory contents in the process.

  5. According to Calif · details withheld

    Code execution

    According to Calif, the end result is code execution via the JVM’s code cache. A failed attempt can crash the JVM, but the attack can often be repeated.

What Java4Shell is not

  • Not a second Log4Shell: there is no single string that works everywhere. Each application needs its own exploit chain.
  • Not a bug in your code: the flaw is in the JVM. An application update only helps if it ships with a patched runtime.
  • Not exploitable everywhere: ARM servers, x86 processors without AVX-512 VBMI and standard builds of Java 8 and 11 are not affected.

Why the flaw is still urgent

  • A crash is easy to trigger. That alone can take services down, even without a full exploit.
  • Exploits exist: VulnCheck offers one to its customers, and according to their own claims, Wiz and Immersive have built their own.
  • Java is inside many things that people do not think of as Java. Jira, Confluence, Elasticsearch, Jenkins and Keycloak often ship with their own runtime.
  • Modern hardware is affected: Intel Xeon of the Ice Lake to Granite Rapids generations and AMD EPYC from Zen 4 onward support AVX-512 VBMI, which covers many current servers and cloud instances.
Assessment

Why the ratings differ

The scores differ mainly on one question: how difficult is the attack? Oracle rates the attack complexity as high without further explanation; according to Calif, each application needs its own exploit chain. This does little to change the urgency.

9.2CVSS 4.0 according to Calif

“Critical” under CVSS 4.0. Calif has not published a vector. [1]

8.1CVSS 3.1 according to Oracle

“High”, because Oracle rates the attack complexity as high. Red Hat’s preliminary score is 9.8. [2][4][5][49]

NoIn the CISA KEV catalog

As of November 18, no confirmed exploitation and no EPSS score yet. CISA nevertheless issues an explicit warning. [11][10][48]

53Java4Shell-like requests

From three IP addresses to GreyNoise’s sensors, so far without any successful intrusion (November 18, 11:48 am CET). [31]

A Log4Shell moment, but not a Log4Shell

As in December 2021, a flaw is hitting the Java world across the board, and once again everyday data is turned into a weapon. Unlike Log4Shell, however, there is no universal attack: each application needs its own exploit profile, and only certain processors are affected. VamiSec assessment: this lowers the risk of mass compromise, not the risk of targeted attacks on exposed services. [1][44][34]

Found with AI, exploit within hours

According to Calif, OpenAI’s AI tool Codex provided the decisive clue. Quang Luong needed one hour to find the flaw and two more hours for the first working exploit; the AI costs were less than $200. According to its own claims, Wiz built a proof of concept within two hours. VamiSec assessment: the time between discovery and a working exploit is shrinking, and patch processes must keep pace. [1][44][45][33]

Disclosure after a leak

A coordinated disclosure had originally been planned. But hints were already circulating before the patch, including in a warning from South Korea’s cybersecurity agency NCSC to public bodies. Calif therefore published the technical details on patch day itself, but is withholding the application-specific exploit chains until operators have been able to update. [35][46][1]

Timeline

From fast decoder to critical flaw

The faulty processor path entered the JVM as a performance optimization and ran unnoticed for years. Disclosure, patch and warnings then followed within hours.

  1. Vendor

    Fast Base64 decoder for AVX-512

    With JDK-8268276, an Intel developer contributes Base64 decoding with AVX-512 instructions to the development of Java 18, which is released in March 2022. [7]

  2. Vendor

    Java 17.0.6 adopts the decoder

    The code is backported to Java 17 and included from version 17.0.6, and subsequently in all newer versions. Java 8 and 11 have not received it. [8][35]

  3. Vendor

    The fix is prepared under wraps

    In the OpenJDK project, the fix JDK-8393212 is created under the inconspicuous title “Base64 optimization improvements”. Four lines redirect short remainders with padding characters to the regular Java code. The CVE number is reserved on October 22. [6][35][4]

  4. Threat

    The flaw leaks out

    Even before the patch, South Korea’s cybersecurity agency NCSC warns public bodies of a Java flaw that requires no authentication. Calif states that the flaw has leaked and announces the details for the evening. [35][46]

  5. Vendor

    Patch, advisory and disclosure

    Oracle publishes its monthly security update with patched Java versions, and the OpenJDK project publishes its advisory. At the same time, Calif discloses the details along with a program that triggers the bug. [1][2][3]

  6. Authority

    CISA and Canada issue warnings

    The US agency CISA calls for immediate patching, and Canada’s Cyber Centre issues warning AL26-029. The Cyber Centre is not aware of any active exploitation. [10][12]

  7. Threat

    Commercial exploit, initial probing

    Since midnight, VulnCheck has been offering its customers a full exploit. GreyNoise maintains its own detection signatures for Java4Shell and counts 53 matching requests from three IP addresses by noon, without any successful intrusion into its sensors. [32][31]

  8. Authority

    BSI, CERT-EU and BACS issue warnings

    Germany’s Federal Office for Information Security (BSI) lists the flaw in its warning WID-SEC-2026-4624 on Oracle Java with the risk rating “high”. CERT-EU advises updating internet-facing applications first, and the Swiss BACS speaks of a critical vulnerability. [14][13][15]

  9. Looking ahead

    Oracle’s next quarterly update

    According to Oracle, the versions it released on November 17 expire with the next regular Critical Patch Update. Plan the next update cycle now. [50]

Affected versions

Which Java installations need the update

A system is only affected if three conditions coincide. You can check the first two here in seconds; the third applies to many web applications.

  • Java 17.0.6 or later

    Affected are the 17 line from 17.0.6 onward, the 21, 25 and 27 lines, and interim versions from 18 onward that are no longer maintained. Standard builds of Java 8 and 11 do not contain the faulty path.

  • x86-64 with AVX-512 VBMI

    For example, Intel Xeon of the Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids generations as well as AMD EPYC or Ryzen from Zen 4 onward. ARM servers and older processors do not use the vulnerable path.

  • Inputs that get decoded

    Attackers must be able to send the application Base64 data that it decodes with java.util.Base64, for example in logins, tokens, cookies or uploads. The MIME decoder does not use the vulnerable path.

Vendor status as of November 18, 2026, noon CET [2][3][17][18][19][21][22][9][23][24][25]
DistributionLinesVersion with fixStatus
Oracle Java SE8 (Performance Pack)172125278u513-perf17.0.21.121.0.13.125.0.5.127.0.1.1Fix availableMonthly security update (CSPU) of November 17. According to Oracle, the Performance Pack for Java 8 is affected; it ships with the JVM from Java 17. [2]
OpenJDK (source code)1721252717.0.21.121.0.13.125.0.5.127.0.1.1Fix availableAdvisory from the OpenJDK Vulnerability Group; fix JDK-8393212 in the release tags. The basis for all other distributions. [3][6]
Amazon Corretto1721252717.0.21.1.221.0.13.1.225.0.5.1.227.0.1.1.4Fix availableThe amazoncorretto Docker image and Amazon Linux have also been updated. A tag such as 17.0.21 does not prove the fix; check java -version in the container. [17][51]
Azul Zulu1721252717.70.20121.54.20125.38.20127.30.201Fix availableZulu version numbers. In the CPU stream for subscribers: 17.69.204, 21.53.202, 25.37.202. Azul Platform Prime: Stable 26.08.110.0 or 26.02.510.0. [18]
SAP SapMachine1721252717.0.21.121.0.13.125.0.5.127.0.1.1Fix availableReleases of November 17. The sapmachine Docker image had not yet been updated on November 18. [19]
Oracle GraalVMJDK 17JDK 21JDK 25EE 21.317.0.21.121.0.13.125.0.5.121.3.20.1Fix availableAccording to Oracle, GraalVM for JDK 17 and 21 as well as GraalVM Enterprise 21.3 are affected; version 25.0.5.1 has also been released. The Community Edition did not yet have a fix on November 18. [20]
Eclipse Temurin (Adoptium)1721252727.0.1.1+4PartialSo far only Java 27 for Linux x64. The builds for 17, 21 and 25 were in testing on November 18, and the eclipse-temurin Docker image was still unpatched. [21]
Microsoft Build of OpenJDK172125–Fix pendingCurrently 17.0.21.0.2, 21.0.13.0.2 and 25.0.5.0.2, all vulnerable. Microsoft does not offer Java 27. [22]
Red Hat (RHEL, Red Hat build of OpenJDK)172125–Fix pendingAccording to bulletin RHSB-2026-018, Red Hat is expediting the fixes. Java 8 and 11 are not affected. [9]
Debian, Ubuntu, SUSE, Alpine17212527–Fix pendingOnly Debian unstable has patched packages. Debian stable, Ubuntu, SUSE and Alpine were still without a fix on November 18. [23][24][25][52]
BellSoft Liberica17212527–Fix pendingLatest builds from October 26, still vulnerable. Important for Spring Boot applications built with Buildpacks. [26]
IBM Semeru (Eclipse OpenJ9)172125–Check noteNot a HotSpot JVM and, based on current information, without the affected code. Confirmation from IBM was still pending on November 18.

Your vendor’s security advisory is what counts. Linux distributions sometimes build fixes into older version numbers, and container images only receive the fix with the next build.

Applications with their own Java runtime

Calif’s tests found these applications to be vulnerable. If they ship with their own runtime, only the vendor’s update helps or, until then, the workaround.

  • Keycloak

    Images 26.8.2-1 and 26.8.2-2 contain an affected OpenJDK 21.0.13; a patched image was not yet available on November 18. The project recommends -XX:-UseBASE64Intrinsics. [27]

  • Atlassian Confluence and Jira

    Confluence 10.2.20 ships with Eclipse Temurin 21.0.13 and Confluence 11.0.1 with Temurin 25.0.5, both without the fix. Atlassian had not commented on Java4Shell by November 18. [28]

  • Jenkins

    The official Docker images use Eclipse Temurin 21.0.13 and 25.0.5, for which there is no fix yet. There was no advisory from the Jenkins project on November 18. [30][21]

  • Elasticsearch

    Versions 8.19.24, 9.4.9 and 9.5.6 ship with Java 27.0.1.0.3, one version before the fix. Elastic had not yet issued a security announcement on Java4Shell on November 18. [29]

  • Artifactory, PingFederate, Kafka, Solr, Gerrit, Spinnaker

    By November 18, there was no statement from these vendors and projects on whether their products are affected.

As of November 18, 2026, noon CET. The commands below show which runtime an application actually uses.

Java check

Paste the output of java -version or enter a version number. The check shows whether your version contains the fix.

Examples:

The check runs only in your browser; nothing is transmitted.

No version entered yet

The result appears as soon as you enter the output of java -version or a version number.

Fixed as of version
Java 1717.0.21.1
Java 2121.0.13.1
Java 2525.0.5.1
Java 2727.0.1.1
Java 8 Performance Pack8u513-perf

RHEL, Debian, Ubuntu and other distributions sometimes include fixes without a new Java version number. There, the package version stated in the distributor’s security advisory is what counts.

CPU check

The vulnerable path only runs if the processor supports AVX-512 VBMI. Paste the flags line from /proc/cpuinfo or the CPU line from jcmd <PID> VM.info.

The check runs only in your browser; nothing is transmitted.

No flags pasted yet

On Linux, grep -m1 flags /proc/cpuinfo returns the line. In VMs and containers, what counts is what the guest system sees.

  • avx512f
  • avx512bw
  • avx512vbmi
  • bmi2

Not affected

  • Standard builds of Java 8 and Java 11
  • Java 17 before version 17.0.6
  • ARM64 servers, such as AWS Graviton or Ampere
  • x86 processors without AVX-512 VBMI, such as Intel Xeon up to Cascade Lake and AMD up to Zen 3

Not affected does not mean permanently safe: a new instance type or a migration to different hardware can activate the vulnerable path. Plan the update anyway.

Find Java runtimes (Linux)

Finds all Java runtimes, including those bundled in applications, via their release file and shows the version and vendor without executing any of the programs found.

Bash · Linux
# Java runtimes incl. bundled ones, read from their release file (nothing is executed)
find / \( -path /proc -o -path /sys -o -path /tmp -o -path /var/tmp -o -path /dev/shm \) -prune -o \
  -type f -name release -print0 2>/dev/null |
xargs -0 -r grep -H -E '^(JAVA_VERSION|IMPLEMENTOR|IMPLEMENTOR_VERSION|JAVA_RUNTIME_VERSION)=' 2>/dev/null

Find Java runtimes (Windows)

The same for Windows servers using PowerShell.

PowerShell · Windows
# Java runtimes incl. bundled ones, read from their release file (nothing is executed)
Get-ChildItem -Path C:\ -Filter release -Recurse -File -ErrorAction SilentlyContinue |
  Select-String -Pattern '^(JAVA_VERSION|IMPLEMENTOR|IMPLEMENTOR_VERSION)=' |
  ForEach-Object { "$($_.Path): $($_.Line)" }

Check running JVMs

Shows for each process the version, whether the workaround is active and whether the JVM has detected AVX-512 VBMI.

Bash · jcmd
# Running JVMs: version, workaround flag, detected CPU features
# (run as the user of each service)
for pid in $(jcmd -l | awk '$2 !~ /JCmd/ {print $1}'); do
  echo "== PID $pid"
  jcmd "$pid" VM.version | sed -n '2,3p'
  jcmd "$pid" VM.flags -all | grep -E ' (UseBASE64Intrinsics|UseAVX) '
  jcmd "$pid" VM.info | grep -m1 -o -E 'avx512_vbmi([^2]|$)' || echo 'no avx512_vbmi'
done

Set the workaround

Disables the vulnerable path until the fix is installed; Red Hat recommends this option because other AVX-512 optimizations remain intact. If JAVA_TOOL_OPTIONS is already set, append the option. Then restart the service and verify with jcmd.

Config
# Docker, Kubernetes, systemd: JVM environment variable
JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics"

# Keycloak
JAVA_OPTS_APPEND="-XX:-UseBASE64Intrinsics"

# Jenkins (Docker image)
JAVA_OPTS="-XX:-UseBASE64Intrinsics"

# Jira and Confluence: bin/setenv.sh
JVM_SUPPORT_RECOMMENDED_ARGS="-XX:-UseBASE64Intrinsics"

# Elasticsearch: config/jvm.options.d/java4shell.options
-XX:-UseBASE64Intrinsics

# After the restart (expected: false)
jcmd <PID> VM.flags -all | grep UseBASE64Intrinsics
Self-check

How well prepared are you for Java4Shell?

Eight questions, answered honestly. “Yes” is always the safe answer. The evaluation stays in your browser.

  1. Do you have a complete list of all Java runtimes, including those bundled in applications and container images?
  2. Are all Java services reachable from the internet running a version with the fix or with the workaround active?
  3. Do you know which of your servers and cloud instances support AVX-512 VBMI?
  4. Have you verified that the workaround is actually active in every running JVM?
  5. Have you asked vendors with a bundled Java runtime about Java4Shell and a date for the update?
  6. Are container images based on a Java base image rebuilt and rolled out after the update?
  7. Does your SOC detect JVM crashes and unexpected processes started by Java services?
  8. Are management interfaces such as Jenkins, Artifactory or the Keycloak console reachable only via VPN or Zero Trust?
Your result

0 of 8 questions answered

The self-check is no substitute for an assessment of your environment.

Action plan

What to do now

Three stages: close the attack surface today, cover the full breadth this week, then improve how you manage runtimes. [1][9][10][39][40]

Today

Close the exposure

  • List Java services reachable from the internet, starting with the applications named by Calif.
  • Install updates where available; otherwise set -XX:-UseBASE64Intrinsics and restart.
  • Verify the effect with jcmd and document it.
  • Where neither is possible: block access from the internet or restrict it to known addresses.
  • Use the queries below to search for crashes and unusual processes.
This week

Cover the full breadth

  • Check the runtimes bundled by vendors and install their updates as soon as they are released.
  • Rebuild container images with an updated base image and roll them out.
  • Patch internal services, batch jobs and Java clients that connect to external servers.
  • Activate WAF rules, such as the AWS Managed Rules “Known bad inputs”: explicitly select version 1.28 and switch the new rules from count to block after a test phase. They complement the patch, but do not replace it.
  • Contact suppliers and record their answers.
30 days

Improve the process

  • Keep Java runtimes permanently in your inventory and in SBOMs.
  • Set patch deadlines for runtime environments, not just for applications.
  • Remove the workaround again after patching to regain performance.
  • Contractually commit vendors with bundled runtimes to update deadlines.
  • Record lessons learned and practice the emergency process for flaws in runtime environments.

For IT operations and the SOC

  • Report patch and workaround coverage daily.
  • Collect and analyze JVM crash logs centrally.
  • Monitor child processes of Java services in endpoint monitoring.

For executive management and the information security officer

  • Make internet-facing systems the priority and follow up on progress.
  • Hold suppliers with bundled runtimes accountable.
  • Clarify whether a suspected incident is reportable under NIS2 or DORA and, as a manufacturer, review your obligations under the Cyber Resilience Act.
Suspect exploitation?

Isolate the system, preserve crash logs and memory dumps, replace all credentials known to the Java process, such as database passwords, tokens or Jenkins credentials, and search for new accounts and web shells. Our CSIRT supports you around the clock.

Report an incident csirt@vamisec.com
Detection

Hunting for traces

Successful exploitation has not been confirmed, but initial attempts have. Start your search from November 16, when the first hints leaked out. Failed attempts often leave traces: JVM crashes, decoding errors and unusual processes. The queries are examples; test them in your environment before use. [31][35][36][37][38]

JVM crashes

Failed attempts can crash the JVM, sometimes only during the next garbage collection; many misdirected writes, however, leave no trace. The log does not always mention Base64. You should therefore examine every unexplained crash, especially if it recurs.

Bash · hs_err logs
# JVM crashes in the last 14 days, Base64 frames flagged
find / \( -path /proc -o -path /sys \) -prune -o \
  -name 'hs_err_pid*.log' -mtime -14 -print 2>/dev/null |
while read -r f; do
  grep -q -E 'Base64\$Decoder|decodeBlock' "$f" && echo "BASE64  $f" || echo "REVIEW  $f"
done

Malformed Base64 input

Probes send Base64 with padding characters but the wrong length; valid Base64 never has a length of four times n plus one. Java reports such input as an IllegalArgumentException. The query counts the typical messages; a sudden increase is suspicious, and the context in the log shows the source.

Bash · application logs
# Base64 decoding errors counted by message (possible probing)
grep -ohE 'Illegal base64 character [0-9a-f]+|Input byte array has (wrong 4-byte ending unit|incorrect ending byte at [0-9]+)|Last unit does not have enough valid bits' \
  /var/log/<app>/*.log | sort | uniq -c | sort -rn | head -20

Java starts a shell

After successful code execution, attackers usually start a shell or download additional tools. On Jenkins and build servers this is normal, so maintain exceptions there.

KQL · Defender XDR
DeviceProcessEvents
| where Timestamp > ago(14d)
| where InitiatingProcessFileName in~ ("java", "java.exe", "javaw.exe")
| where FileName in~ ("sh", "bash", "dash", "cmd.exe", "powershell.exe",
    "pwsh.exe", "curl", "wget", "certutil.exe")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine,
    InitiatingProcessCommandLine

Affected software in your inventory

As soon as Microsoft lists the CVE in Defender Vulnerability Management, this query shows affected installations. Tenable, Qualys and Rapid7 have published their own checks, and Cisco Talos has published Snort rules. Container scanners sometimes miss manually unpacked JDKs.

KQL · Defender Vulnerability Management
DeviceTvmSoftwareVulnerabilities
| where CveId == "CVE-2026-114938"
| summarize Devices = dcount(DeviceId) by SoftwareVendor, SoftwareName, SoftwareVersion
| order by Devices desc

Hits are indications, not proof, and their absence does not prove that nothing has happened. If you find something, treat the system as compromised until proven otherwise.

NIS2, CRA and DORA

What regulation says about it

The flaw itself is not a reportable incident. What attackers do with it can become reportable, and manufacturers have obligations of their own.

  • Handling vulnerabilities is mandatory

    NIS2 requires essential and important entities to have risk management in place that includes vulnerability handling. Anyone who leaves a critical flaw in internet-facing systems open for days may have to justify it.

  • Reporting deadlines in an emergency

    If an attack leads to a significant security incident, the following applies in Germany: early warning to the BSI within 24 hours, notification within 72 hours, final report no later than one month after the notification.

  • Manufacturers: Cyber Resilience Act

    Since September 11, 2026, manufacturers have had to submit an early warning within 24 hours if a vulnerability in one of their own products with digital elements is actively exploited, even if it lies in a bundled Java runtime. The obligations to handle vulnerabilities and provide updates apply from December 11, 2027.

  • Financial sector: DORA

    Financial entities assess ICT incidents under DORA and report major ones to their supervisory authority. Java products from service providers are part of ICT third-party risk management.

How VamiSec supports you

Find, secure, prove

From a short-notice exposure check to a lasting overview of your Java runtimes.

Acute

CSIRT and Compromise Assessment

If you suspect an incident, we determine whether a JVM has been compromised: crash logs, processes, credentials and network traffic, across servers and containers.

Compromise Assessment
Attack surface

Find exposed Java services

Within an authorized scope, VamiRedteam checks from the outside which Jira, Confluence, Jenkins or Keycloak instances are reachable.

VamiRedteam
Cloud

Cloud workloads with Wiz

As a member of the Wiz Partner Alliance, we help Wiz customers find and prioritize affected Java runtimes in VMs and containers.

VamiSec and Wiz
Detect

Managed Detection & Response

We monitor servers and containers for JVM crashes, suspicious child processes and attempts to download additional tools, and respond around the clock.

MDR at VamiSec
Supply chain

SBOM and runtime inventory

We make visible which Java runtimes are contained in your products, images and applications, and keep the inventory up to date.

SBOM at VamiSec
Prevent

Zero-day monitoring

We promptly match newly disclosed flaws such as Java4Shell against your attack surface, so that you can act before regular patch cycles take effect.

Zero-day monitoring
VamiGRCAgentic GRC platform

VamiGRC: match vulnerabilities against assets, manage deadlines, maintain evidence

VamiGRC matches CISA KEV, NVD and EPSS against your assets, products and SBOMs. When a flaw such as CVE-2026-114938 appears, you see which of your recorded assets are affected and manage actions and deadlines through to evidence.

  • CISA KEV, NVD and EPSS are matched against your assets, products and SBOMs.
  • Evidence from connected systems is updated along with its source rather than at audit time.
  • When an incident is recorded, a deadline timer starts for NIS2; VamiAI drafts notifications, and your team reviews and submits them.
  • One control, multiple frameworks: implemented once, mapped to NIS2, ISO 27001 and other standards.
  • AI agents handle the routine work according to your approval rules; your team decides.
Valeri Milke, founder and managing director of VamiSec GmbH
Schedule a call

Let’s talk about your Java landscape

Whether it is an exposure check, a workaround rollout or evidence for NIS2 and the CRA, Valeri Milke and the VamiSec team help you derive concrete next steps from this briefing.

“IT security and compliance without AI is a vulnerability.”

Valeri MilkeFounder & Managing Director · VamiSec GmbHISO/IEC 27001 & ISO/IEC 42001 Lead Auditor
20Years of GRC experience of the founder
ISO 27001VamiSec is itself certified
T Cloud PublicOperation in German data centers
24/7CSIRT for security incidents
FAQ

Frequently asked questions about Java4Shell

What is Java4Shell?

Java4Shell is the name for CVE-2026-114938, a flaw in the Base64 decoder of OpenJDK’s HotSpot JVM. On x86-64 processors with AVX-512 VBMI, the accelerated decoder writes beyond the end of its memory buffer when it processes crafted input. Calif disclosed the flaw on November 17, 2026 and, according to its own claims, used it to achieve code execution without authentication in widely used Java applications.

Am I affected?

Three conditions must coincide: a Java version from 17.0.6 onward, which also includes 21, 25 and 27 as well as interim versions from 18 onward; an x86-64 processor with AVX-512 VBMI; and an application that decodes externally supplied Base64 data with java.util.Base64. You can check the first two points with the Java check and the CPU check on this page.

Which versions contain the fix?

On November 17, Oracle released Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and 8u513-perf for the Java 8 Enterprise Performance Pack. The source code releases of the OpenJDK project and SAP SapMachine carry the same version numbers. Amazon Corretto delivers 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4, and Azul Zulu delivers versions 17.70.201, 21.54.201, 25.38.201 and 27.30.201. Other vendors are following suit; the table above shows the current status.

Is this like Log4Shell?

Only in its breadth. In 2021, Log4Shell could be triggered almost everywhere with a single string. Java4Shell requires a suitable processor and its own exploit chain for each application. Crashing a JVM, on the other hand, is easy.

What does -XX:-UseBASE64Intrinsics do?

The option disables hardware-accelerated Base64 processing, and the JVM then uses the regular Java code. This closes the vulnerable path but costs some performance in Base64-heavy applications. Alternatively, -XX:UseAVX=2 disables AVX-512 entirely, with a greater loss of performance; on ARM systems, this option prevents the JVM from starting. Neither option replaces the patch.

Is Java4Shell already being exploited?

As of November 18, successful exploitation has not been confirmed; the flaw is not in CISA’s KEV catalog. However, GreyNoise has recorded the first requests from three IP addresses that look like Java4Shell attempts, and VulnCheck offers its customers a full exploit. Expect attacks.

Is there public exploit code?

Calif has published a program that triggers the bug without executing code. Further proofs of concept and detection rules are circulating on GitHub. Calif is withholding the application-specific chains. Do not download third-party exploit code without checking it: supposed exploits are regularly malware themselves.

Are ARM servers and the cloud affected?

ARM servers such as AWS Graviton are not; the faulty code only exists for x86-64. In the cloud, it depends on the instance type: many current Intel and AMD instances support AVX-512 VBMI. According to Semgrep and a note in the Azure Functions project, the managed Java runtimes of AWS Lambda and Azure Functions use only the C1 compiler by default and therefore do not use the vulnerable path, as long as nobody changes this with a startup option. For Lambda, this does not apply to Java 25 with SnapStart or Provisioned Concurrency. Check the CPU features in the VM or container.

Our application ships with its own Java runtime. What should we do?

Ask the vendor for a version with a patched runtime and, until then, set the workaround in the application’s startup configuration, for example in bin/setenv.sh for Jira and Confluence or in config/jvm.options.d for Elasticsearch. By November 18, only Keycloak had published a recommendation, but no patched image was available there yet.

How does VamiSec support you?

At short notice, we check which Java services are reachable and affected, roll out the workaround and updates with you, build detection rules and investigate suspected cases with a compromise assessment and our CSIRT. With VamiGRC, you manage vulnerabilities, deadlines and evidence for NIS2 and the CRA.

Sources

Sources and further information

The information is based on publications by Calif, Oracle, the OpenJDK project, authorities, vendors and security researchers up to November 18, 2026, noon CET. Assessments by VamiSec are identified as such.

  1. [1]Calif: Java4Shell: Write once, RCE everywhere,
  2. [2]Oracle: Oracle Critical Security Patch Update Advisory – November 2026,
  3. [3]OpenJDK Vulnerability Group: OpenJDK Vulnerability Advisory: 2026/11/17,
  4. [4]CVE Program: CVE Record CVE-2026-114938,
  5. [5]NIST National Vulnerability Database: CVE-2026-114938 Detail,
  6. [6]OpenJDK (GitHub): 8393212: Base64 optimization improvements,
  7. [7]OpenJDK (GitHub): 8268276: Base64 Decoding optimization for x86 using AVX-512,
  8. [8]OpenJDK (GitHub): jdk17u: Backport of 8268276 (ab 17.0.6),
  9. [9]Red Hat: RHSB-2026-018: Remote Code Execution via memory corruption on x86-64 systems – OpenJDK (CVE-2026-114938),
  10. [10]CISA: Critical Java Vulnerability Requires Immediate Patching,
  11. [11]CISA: Known Exploited Vulnerabilities Catalog,
  12. [12]Canadian Centre for Cyber Security: AL26-029 – Critical vulnerability impacting Oracle Java – CVE-2026-114938,
  13. [13]CERT-EU: Security Advisory 2026-021: High Severity Vulnerability in Java SE and OpenJDK,
  14. [14]BSI / CERT-Bund: WID-SEC-2026-4624: Oracle Java und GraalVM: Mehrere Schwachstellen,
  15. [15]Bundesamt für Cybersicherheit BACS: Java4Shell: Kritische Schwachstelle in Java – Sicherheits-Updates sofort einspielen,
  16. [16]Cyber Security Agency of Singapore: High-Severity Vulnerability in Java Products,
  17. [17]Amazon Corretto (GitHub): Corretto 17 Change Log,
  18. [18]Azul: November 2026 Monthly Update Release Notes,
  19. [19]SAP (GitHub): SapMachine Releases,
  20. [20]Oracle: GraalVM Release Calendar
  21. [21]Eclipse Adoptium (GitHub): Temurin Release-Tracking, Issue 326,
  22. [22]Microsoft Learn: Download the Microsoft Build of OpenJDK,
  23. [23]Debian: Security Tracker: CVE-2026-114938,
  24. [24]Ubuntu: CVE-2026-114938,
  25. [25]SUSE: CVE-2026-114938,
  26. [26]BellSoft (GitHub): Liberica JDK Releases,
  27. [27]Keycloak: Java4Shell: What Keycloak admins need to do (CVE-2026-114938),
  28. [28]Atlassian: Bundled Tomcat and Java versions (Confluence),
  29. [29]Elastic: Elasticsearch 8.19.24, 9.4.9, 9.5.6 Security Update (ESA-2026-227),
  30. [30]Jenkins (GitHub): jenkinsci/docker Releases,
  31. [31]GreyNoise: Java4Shell (CVE-2026-114938) Activity 2026,
  32. [32]VulnCheck: Java4Shell CVE-2026-114938: Fine, I Guess We’ll Do This Again,
  33. [33]Wiz: CVE-2026-114938 OpenJDK RCE (Java4Shell): Everything You Need to Know,
  34. [34]Tenable: Java4Shell (CVE-2026-114938): Frequently Asked Questions About OpenJDK RCE Vulnerability,
  35. [35]Endor Labs: Java4Shell (CVE-2026-114938): Pre-Auth Heap Overflow in OpenJDK,
  36. [36]Cisco Talos: CVE-2026-114938: Critical vulnerability in OpenJDK JAVA,
  37. [37]Datadog Security Labs: Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938),
  38. [38]ThreatDefence: Java4Shell CVE-2026-114938: Java 17 to 27 Fixes and Hunting,
  39. [39]Amazon Web Services: AWS Managed Rules changelog,
  40. [40]Microsoft Tech Community: Addressing Java4Shell (CVE-2026-114938): Upgrade Guidance and Azure WAF Mitigations,
  41. [41]Semgrep (GitHub): detection-scripts: CVE-2026-114938,
  42. [42]Azure Functions Java Worker (GitHub): Issue 909 zu CVE-2026-114938,
  43. [43]heise online: Java4Shell: Gefährlicher Bug in Java,
  44. [44]BleepingComputer: Critical Java4Shell flaw allows RCE attacks on major Java applications,
  45. [45]The Record: CISA warns of ‘Java4Shell,’ an AI-found Java bug touching most of the Fortune 500,
  46. [46]SecurityWeek: Java4Shell Vulnerability Puts Many Enterprise Applications at Risk of Takeover,
  47. [47]The Register: Oracle reveals fix-this-ASAP-grade Java4Shell bug that allows attacks on many third-party apps,
  48. [48]FIRST: Exploit Prediction Scoring System (EPSS): CVE-2026-114938,
  49. [49]Red Hat: CVE-2026-114938,
  50. [50]Oracle: JDK 17.0.21.1 Release Notes,
  51. [51]Amazon Corretto (GitHub): Corretto 27 Change Log (27.0.1.1.4),
  52. [52]Alpine Linux: Package index: openjdk*-jdk (edge, x86_64),

This briefing is no substitute for legal advice or an assessment of your environment.

Act now

Patching comes first.
Knowing your Java runtimes makes you faster next time.

Arrange a no-obligation initial consultation: together, we will clarify your exposure, the workaround and your update plan.