Oracle shipped fixed Java builds on 17 November 2026 for Java4Shell CVE-2026-114938, a reported unauthenticated remote code execution flaw rated 9.2 under CVSS 4.0 in early reports. Aikido lists Java 17, 21, 25 and 27 as affected and says patching is the only fix. WordPress and Joomla don't run on Java, but the server behind them may.
Key takeaways
- Oracle's fixed builds for CVE-2026-114938 (Java4Shell), released 17 November 2026, are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1; Java 8 and 11 are not affected by this CVE.
- The vulnerable component was not public on day one, and no in-the-wild exploitation had been reported.
- Patching only counts after Java processes restart and container images are rebuilt.
- Give your host 48 hours to name every Java runtime and version, and recheck 24 to 48 hours after details go public.
What is Java4Shell CVE-2026-114938?
Java4Shell is the nickname for CVE-2026-114938, a reported Java flaw that lets an attacker run code on a server without logging in. Aikido’s advisory, written on 17 November 2026, says the vulnerable component and exploit conditions were not yet public, with details expected later that day.
Aikido had seen no exploitation in the wild but warns that attacks can follow quickly once details land. Patch now instead of waiting for a proof of concept.
The score is also unsettled. Oracle rates Java flaws under CVSS 3.1, and its highest Java SE score in the November update is 8.1. Aikido says the two figures may describe different issues.
Which Java builds are affected?
Treat every Java line you run as affected. Aikido’s summary names 17, 21, 25 and 27, though one passage in the same post ties the CVE to Java 17 alone.
| Java line | Oracle fixed build | Status on 17 Nov |
|---|---|---|
| 17 | 17.0.21.1 | Affected; named in early reports |
| 21 | 21.0.13.1 | Listed by Aikido |
| 25 | 25.0.5.1 | Listed by Aikido |
| 27 | 27.0.1.1 | Listed by Aikido |
| 8 and 11 | n/a | Not affected; other November fixes apply |
Temurin, Corretto, Zulu and Linux distribution packages ship fixes on their own schedules and may use different build numbers, so check each vendor’s advisory or changelog. The full lists live in Aikido’s Java4Shell advisory and Oracle’s November 2026 Java SE release notes.
Why should a WordPress or Joomla owner care?
WordPress and Joomla are PHP applications, so no theme or plugin is affected. The Java running next to them is another matter: Elasticsearch or Solr, a hosting panel component, a monitoring agent, or an old container nobody has looked at in a while.
Aikido’s scope covers Oracle JDK, JRE, GraalVM and JavaFX, third-party OpenJDK builds (Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft and Red Hat), distribution packages such as openjdk-17, and JDKs bundled in applications and container images. As we explained in PHP2Shell on shared hosting, a runtime flaw on a shared server is something only the host can patch.
What should you ask your host today?
Ask for the exact vendor and version of every Java runtime on your server, not a one-line “Java is updated.” Put four questions in the ticket:
- Which Java runtimes run on the server hosting my site, including panels, search services and containers?
- What vendor and full version string does each have, and which face the internet?
- Has each moved to its vendor’s fixed build?
- Were the Java processes restarted and container images rebuilt?
A patched package does nothing for a process still running the old code, and updating Java on the container host leaves runtimes inside images untouched. Start with internet-facing services: Aikido says anything reachable from outside “is the likeliest to be hit once details are public.”
What if your host stalls?
Give the host 48 hours from your ticket. If the reply stays vague (“we keep everything updated”), escalate to a named contact and ask in writing whether any Java service on your plan faces the internet.
Meanwhile, watch for new admin users, unfamiliar PHP files and edits to .htaccess or wp-config.php. Our antivirus website protection flags new or changed code in your site files. A web firewall filters traffic but does not patch the host’s Java.
Recheck 24 to 48 hours after details go public. A host that still can’t name its Java versions by then gives you a reason to move.
How do you check Java versions on your own VPS?
Aikido users can run the dashboard’s “Am I affected?” check. Otherwise, don’t stop at java -version: it reports only the runtime on your PATH, not a private runtime an installer dropped in its own folder or a JDK inside an image.
# running Java processes
ps -eo pid,args | grep [j]ava
ls -l /proc/<pid>/exe
# installed packages (Debian/Ubuntu, RHEL family)
dpkg -l | grep -i -E 'jdk|jre'
rpm -qa | grep -i -E 'jdk|jre'
# Java inside running containers
docker ps --format '{{.Names}}' | xargs -I{} docker exec {} java -version
# restart after updating
systemctl restart <service-name>
Also check service definitions, application directories and scheduled jobs. After each restart, confirm the version the running process reports, not just what the package manager lists.
FAQ
Does WordPress use Java, and am I at risk?
No, WordPress and Joomla run on PHP. Your risk comes from Java services on the same server, such as search engines, panel components or containers.
Which Java builds should my host be on?
Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Temurin, Corretto, Zulu and Linux packages may use different numbers, so check each vendor's advisory.
Is there a workaround if the host cannot patch today?
None has been published. Aikido says patching is the fix, starting with internet-facing services.
If you can’t tell which runtimes sit behind your site, or you want someone watching it while the host patches, our website protection package covers monitoring, firewall and cleanup.
