Cyber Security Services ยท Trusted by Fortune 100 enterprises, growing businesses, and MSPs since 2014

Insights · Threat Alerts

Java4Shell (CVE-2026-114938): What It Is and What to Do Now

Cyber Security Services · Last updated November 19, 2026

On November 17, 2026, Oracle and the OpenJDK project fixed a memory bug in Java itself, nicknamed "Java4Shell." A short, malformed piece of text sent to an affected Java application can crash it and, in some cases, let an attacker run code without logging in. CISA has urged organizations to patch immediately. The good news: only some Java systems are exposed, and there is a simple temporary fix.

The short version

  • Affected: Java 17.0.6 and later, plus Java 21, 25 and 27, from any vendor, running on newer Intel or AMD server chips. Standard Java 8 and 11, and ARM systems, are not affected.
  • Fix: Install the November 2026 Java update from your vendor, then restart the application.
  • Can't patch today? Restart Java with -XX:-UseBASE64Intrinsics as a stopgap.
  • Start with: internet-facing login systems such as Keycloak and PingFederate, then Jira, Confluence, Jenkins and Artifactory.

As of November 19, there are no public reports of attacks using this flaw.

Jump to the step-by-step checks: copy-and-paste commands for Linux and Windows servers, and what the results mean.

What is Java4Shell?

Java includes a speed-up for decoding Base64, a common way of turning data into plain text. Logins, tokens and file uploads often use Base64. On newer processors, Java uses special chip instructions (called AVX-512) to decode faster. That fast code has a bug. When it receives a short, malformed Base64 string, it writes about 62 bytes past the end of its memory buffer before Java rejects the input. (Qualys, Rapid7)

Writing past a buffer can damage other data in memory. Depending on the application, that can crash Java, leak data held in memory such as keys or tokens, or give an attacker control of the application. Because the bug is in Java and not in any one product, many applications that run on Java can be affected without any flaw of their own.

The flaw was found by the security firm Calif, the same team that disclosed the PHP2Shell flaw earlier this year (we offer a free PHP2Shell website check). (Calif)

How serious is it?

Ratings differ. Calif rates it 9.2 out of 10 (Critical). Oracle rates it 8.1 (High) because a working attack takes effort. Both are right in their own way:

  • Crashing an affected service is easy. Researchers have reproduced the crash independently. A short burst of requests can take down an exposed service. (OX Security)
  • Taking control is harder. Calif showed code execution without a login against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate in their default settings, and with a login against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Each product needs its own custom attack, and Calif has held back those attack details for now. (Calif)

One firm, OX Security, estimates that under 1% of Java systems can be crashed remotely and about 0.12% are realistic targets for a takeover. That is an estimate built on assumptions, not a measurement, but it matches the picture: a serious bug with a narrow reach. (OX Security)

Am I affected?

A Java application is at risk only if all four of these are true:

ConditionAffectedNot affected
Java version17.0.6 and later, 21, 25, 27 (any vendor: Oracle, Temurin, Corretto, Microsoft, Azul, Red Hat and others); Oracle 8u511-perfStandard Java 8 and 11; 17.0.0 to 17.0.5; builds that include the November fix
Processorx86-64 chips with AVX-512 VBMI: Intel Xeon Ice Lake and newer, AMD EPYC and Ryzen Zen 4 and newerARM64 (including AWS Graviton and Apple silicon); older Intel and AMD chips
Code pathThe application decodes outside input with Java's standard Base64 decoderApplications that never decode untrusted Base64
ExposureReachable from the internet, worst of all before loginInternal only (lower risk, still patch)

Sources: Calif, Qualys, OX Security.

The catch: Java hides. Many products ship their own copy of Java inside the application folder or container image. Running java -version on the server can show a safe version while Jenkins, Confluence or an appliance quietly uses an older one. Operating system updates do not touch these bundled copies. Check what each running application actually uses.

How to check your systems, step by step

These steps only read information. They do not change anything, restart anything or need new software. Each one is a single line you copy and paste.

Where to run them: on each server that runs Java-based software, such as Jira, Confluence, Jenkins, Keycloak, Elasticsearch, Kafka, vendor applications and your own in-house Java apps. Not sure which servers run Java? Run step 2 on all of them. It is harmless and will tell you.

Who should run them: anyone with an administrator account on the server. Hand this section to your IT team or IT provider if that is not you.

1Open a command window on the server

Linux server

  1. Connect to the server the way you normally do: an SSH program such as Terminal, PuTTY or Windows Terminal (for example ssh yourname@server-name), or your cloud provider's web console.
  2. Type sudo -i and press Enter. Enter your password if asked. This gives you administrator rights so the checks can see every application.

Windows server

  1. Sign in to the server, for example with Remote Desktop.
  2. Click Start and type PowerShell.
  3. Right-click Windows PowerShell and choose Run as administrator. Click Yes if Windows asks.

To run a command: click Copy on the box below, click inside the command window, paste (right-click in PowerShell and most SSH windows, or Ctrl+Shift+V in Linux terminals), then press Enter.

2Find every copy of Java and its version

Run both commands for your server type. The first shows Java that is running right now. The second searches the whole disk, which also finds copies of Java hidden inside application folders.

Linux server

Linux: Java running now
for p in $(pgrep -x java); do j=$(readlink -f /proc/$p/exe); echo "Running process $p uses $j"; "$j" -version 2>&1 | head -n 1; done
Linux: every copy on disk (can take a few minutes)
find / \( -path /proc -o -path /sys \) -prune -o -type f -name java -path '*/bin/*' -print 2>/dev/null | while read j; do echo "$j"; "$j" -version 2>&1 | head -n 1; done

Windows server (PowerShell)

Windows: Java running now
Get-CimInstance Win32_Process -Filter "Name like 'java%'" | ForEach-Object { "Running process $($_.ProcessId) uses $($_.ExecutablePath)"; cmd /c "`"$($_.ExecutablePath)`" -version 2>&1" | Select-Object -First 1 }
Windows: every copy on drive C: (can take several minutes)
Get-ChildItem -Path C:\ -Recurse -Filter java.exe -ErrorAction SilentlyContinue | ForEach-Object { $_.FullName; cmd /c "`"$($_.FullName)`" -version 2>&1" | Select-Object -First 1 }

On Windows, if the server has other drives, run the second command again with C:\ changed to D:\, E:\ and so on. If nothing prints, no Java was found in that place.

Each result shows a file location followed by a version line, like this:

/opt/atlassian/jira/jre/bin/java
openjdk version "17.0.18" 2026-01-20

3Read your results

Look at the number in quotes on each version line:

The version line showsWhat it means
"1.8.0_..." (Java 8) or "11.0..." (Java 11)Not affected by Java4Shell. Exception: Oracle's Java 8 Performance Pack, which shows perf in the line.
"17.0.0" to "17.0.5"Not affected by this flaw (but out of date, so update anyway).
"17.0.6" or higher, or any "21...", "25..." or "27..."Possibly affected. Go to step 4, and plan the update.
17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or higherFixed (Oracle and Microsoft numbering). Other vendors may number their fixed builds differently, so check the vendor's advisory.
"18...", "19...", "20...", "22...", "23...", "24..." or "26..."These versions no longer receive updates. Treat as affected and move to a supported version.

The location tells you which application the copy belongs to. A path such as /opt/atlassian/jira/jre or C:\Program Files\Jenkins\jre means that product brought its own Java, so the fix usually comes as an update to that product. Ask its vendor.

4Check the processor

The bug can only be triggered on certain newer Intel and AMD processors. This step tells you how urgent a possibly affected server is.

Linux server

Linux: processor check
grep -o -w -E 'avx512f|avx512bw|avx512vbmi|bmi2' /proc/cpuinfo | sort -u
  • All four words print (avx512bw, avx512f, avx512vbmi, bmi2): this processor can trigger the bug. If step 3 said "possibly affected," this server is affected. Patch it first if it is reachable from the internet.
  • Fewer than four print: this server cannot trigger Java4Shell. Still apply the update in your normal patch cycle.

Windows server (PowerShell)

Windows: processor name
Get-CimInstance Win32_Processor | Select-Object -ExpandProperty Name

Windows has no simple built-in command for the exact check, so compare the name with this list:

  • Likely affected: Intel Xeon Scalable 3rd generation and newer (model numbers such as Gold 6338, Gold 6430, Platinum 8380, Platinum 8580), Intel Xeon 6 with performance cores, and AMD EPYC 9004, 9005, 8004 or 4004 series.
  • Not affected: ARM processors, Intel Xeon Scalable 1st and 2nd generation (model numbers such as Gold 6148 or 6248) and older Xeon E5 and E7 chips.
  • Not sure? Treat the server as affected. Updating Java is the fix either way.

Cloud servers report the processor of the machine they run on, so these commands work there too.

5If you run containers

Java inside a container is separate from Java on the server. On a Linux server that runs Docker, this lists the Java version inside each running container:

Linux: Java inside each running Docker container
for c in $(docker ps -q); do echo "Container $(docker inspect -f '{{.Name}}' $c)"; docker exec $c sh -c 'java -version 2>&1 | head -n 1' 2>&1; done

If a container shows java: not found, Java is not installed in the usual place inside it, or the app was built without it. Ask the team that builds the container image. For Kubernetes and cloud container services, ask your platform team or use a vulnerability scanner that checks container images. A container is fixed only when its image is rebuilt with patched Java and redeployed.

6After the stopgap: confirm it took effect

If you restarted an application with -XX:-UseBASE64Intrinsics while you wait for the patch, this lists every running Java process that has the setting:

Linux: processes with the stopgap
ps -eo pid,args | grep [U]seBASE64Intrinsics
Windows: processes with the stopgap
Get-CimInstance Win32_Process -Filter "Name like 'java%'" | Where-Object CommandLine -like '*UseBASE64Intrinsics*' | Select-Object ProcessId, CommandLine

Each application you protected should appear. If one is missing, it was not restarted with the setting. Some applications read Java settings from a configuration file or the JAVA_TOOL_OPTIONS variable instead of the command line, so they may not show here; check that application's startup settings.

Faster for many servers: use a scanner

If you manage more than a handful of servers, a vulnerability scanner is quicker. Qualys, Rapid7 and others added Java4Shell checks on November 18. These checks look at version numbers only, not the processor or settings, so a finding means "possibly affected" until you confirm it with step 4. (Rapid7)

Calif also publishes a safe test program that shows whether a given Java installation has the bug. Run it on a test machine only. Do not download "proof of concept" code from GitHub or social media: fake exploit repositories for news-making flaws often contain malware. (Calif, OX Security)

What to do, in order

  1. Patch internet-facing login systems first. Keycloak, PingFederate and anything else that checks passwords or tokens before login.
  2. Then internet-facing team tools. Jira, Confluence, Jenkins, Artifactory and other Java services that handle logins, tokens or uploads.
  3. Then internal Java systems. Kafka, Solr, Elasticsearch, Gerrit, Spinnaker and in-house Java applications.
  4. Restart after patching. A running Java process keeps the old code until it restarts. Rebuild and redeploy container images that bundle Java.
  5. Confirm. Check that each running process now reports a fixed version.

Patch order based on Qualys and OX Security.

Fixed versions

LineOracle fixed build
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

Source: Oracle November 2026 Critical Patch Update. As of November 19, Amazon (Corretto 17.0.21.1.2) and Microsoft (Build of OpenJDK 17.0.21.1, 21.0.13.1 and 25.0.5.1) had also released fixed builds. Other vendors, including Eclipse Temurin and Red Hat, publish on their own schedules, so check each vendor's advisory and confirm the build names CVE-2026-114938. (Qualys, Microsoft)

If you cannot patch today

Restart the Java application with this setting, which turns off only the faulty fast decoder. Java falls back to its normal decoder, which can be slower for applications that decode large amounts of data:

-XX:-UseBASE64Intrinsics

A broader option, -XX:UseAVX=2, turns off all AVX-512 speed-ups on Intel and AMD. Never apply it to ARM systems: Java will not start. Both settings need a restart, and neither replaces the patch. (Calif, Rapid7)

While you wait, take login, build and collaboration consoles off the open internet or put them behind a VPN. CISA also suggests checking and limiting Base64 input at the application edge. Researchers caution that the attack string is very short, so size limits and proxy buffering alone will not stop it. (CISA, Qualys)

Signs something is wrong

  • Unexpected crashes or restarts of internet-facing Java services, and new hs_err_pid crash files
  • Bursts of Base64 decoding errors (IllegalArgumentException) in application logs
  • Java processes starting a command shell or opening new outbound connections
  • Java runtimes on servers that are not in your inventory

If you see these on an exposed service, treat secrets held in that application's memory, such as keys, tokens and passwords, as exposed and rotate them. (OX Security, Qualys)

For regulated organizations

On November 18, the New York Department of Financial Services sent an industry letter asking regulated entities to review their inventories for affected Java runtimes, including those bundled in third-party software, coordinate with their software providers, and confirm that patches or other mitigations are in place. The letter sets no reporting deadline. Even outside New York, documenting what you checked, what you patched and when is good evidence for auditors and cyber insurers. (NY DFS)

Why this one matters beyond Java

According to Qualys, the researchers say they found this bug with AI assistance in about an hour and had a first working attack two hours later. (Qualys) Whether or not those numbers hold for every case, the time between a flaw being found and being usable is shrinking. An annual scan or a yearly penetration test will miss flaws like this for most of the year. Knowing where every runtime lives, and testing exposed systems as new flaws appear, is what lets a team answer "are we affected?" in hours instead of weeks.

That is why we built AutoPentests, our continuous penetration testing service. It tests your internet-facing systems every day with real attack methods, adds checks for newly disclosed flaws as they are published, and alerts you when something critical turns up. Instead of waiting for next year's pentest, you know within days whether a new vulnerability affects you.

Frequently asked questions

Is this like Log4Shell?

The name is similar, but the reach is much smaller. Log4Shell affected a logging library used almost everywhere and was easy to exploit. Java4Shell needs a specific Java version, specific processors and an application that decodes outside Base64 input, and taking control needs a custom attack per product. Crashing an exposed service is easy, though, so patch promptly.

We only run Java 8 or Java 11. Are we safe from this one?

Standard Java 8 and 11 builds are not affected. The exception is Oracle's Java 8 Enterprise Performance Pack build 8u511-perf, which is fixed in 8u513-perf. Older Java versions have other unpatched flaws, so plan an upgrade anyway.

Our servers run in the cloud. Does that change anything?

It depends on the processor. Many cloud virtual machines run on Intel or AMD chips that have AVX-512 and are affected. Machines on ARM processors, such as AWS Graviton, are not. Run the processor check above on the machine itself.

Do desktop computers need the patch?

Mostly this is a server problem, because an attacker needs to send data to the application. Qualys notes that a Java program connecting to a malicious server can also be attacked, so update Java on desktops through your normal patch cycle as well.

Is the flaw being exploited?

As of November 19, 2026, no attacks have been publicly reported and the flaw is not on CISA's Known Exploited Vulnerabilities list. Calif plans to publish its product-specific attack details later, which usually leads to attacks soon after. Patch before that happens.

Need help finding every copy of Java?

We can inventory the Java runtimes across your servers, containers and third-party applications, test your internet-facing systems for exposure, and help you patch in the right order. For ongoing coverage, AutoPentests keeps testing every day so the next Java4Shell does not wait for your annual pentest. If you are seeing crashes you cannot explain, call us at 1-800-390-1053.

Get a Free Consultation

Sources

Get a free consultation

Tell us what you need. A senior consultant replies within one business day, with no obligation.

Urgent, such as a breach in progress? Call 1-800-390-1053.