Hidden Runtime Finder: Java, Ruby and PHP versions vs this week's flaws
The Java your vulnerability scanner reports is rarely the only one. Copies hide in application folders, container images and old installs. Copy read-only commands for Linux, Windows, Docker or Kubernetes, paste the output or an SBOM, and see every runtime against Java4Shell, Ruby2Shell, PHP2Shell and phpAfterShell. Runs in your browser. Nothing you paste is sent to PlayCISO.
Runs in your browser. Nothing you paste is sent to PlayCISO. The commands only read: they install nothing and change nothing. One optional Docker command starts a short-lived container, and says so.
1. Where do your runtimes live?
Pick one or more. Copy a command, run it, and paste the output in step 2.
Linux host
Servers and VMs. Run as a user that can read the whole disk (root, or sudo) so nothing is missed.
- Find every java, ruby and php binary and print its versionshell
find / -xdev \( -name java -o -name ruby -o -name 'ruby[0-9]*' -o -name php -o -name 'php[0-9]*' -o -name php-fpm -o -name 'php-fpm[0-9]*' -o -name php-cgi -o -name 'php-cgi[0-9]*' \) -type f -perm -100 2>/dev/null | while IFS= read -r p; do echo "== $p"; case "${p##*/}" in java) timeout 10 "$p" -version 2>&1 | grep -v '^Picked up' | head -n 3 ;; *) timeout 10 "$p" -v 2>&1 | head -n 1 ;; esac; doneSearches the root filesystem only (-xdev): add other mount points after / if /opt or /srv are separate filesystems. It runs each binary it finds with its version flag (-version or -v), with a 10-second timeout, and changes nothing.
- Java without running anything: read each JDK's release fileshell
find / -xdev -type f -name release 2>/dev/null | while IFS= read -r f; do grep -q '^JAVA_VERSION=' "$f" 2>/dev/null || continue; echo "== $f"; grep -E '^(JAVA_VERSION|IMPLEMENTOR|GRAALVM_VERSION)=' "$f"; done
Every JDK and JRE ships a plain-text file called release with JAVA_VERSION and IMPLEMENTOR. This only reads files.
- Debian / Ubuntu: installed runtime packagesshell
dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' 2>/dev/null | grep -E '^ii +(openjdk-[0-9]+-j|temurin-|zulu[0-9]|java-[0-9]+-amazon-corretto|libruby|ruby[0-9]|php[0-9.]+-(cli|fpm|cgi|common)|libapache2-mod-php)'Reads the package database. Distribution packages can carry a backported fix under an older version number, so the result may say "Unknown" and point you to the distribution's advisory.
- RHEL / Rocky / Alma / Fedora / Amazon Linux / SUSE: installed runtime packagesshell
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE}\n' 2>/dev/null | grep -E '^(java-(1\.8\.0|[0-9]+)-(openjdk|amazon-corretto)|temurin-|zulu[0-9]|ruby |ruby-libs |php |php-(cli|fpm|common) )' | sortReads the RPM database.
- Alpine: installed runtime packagesshell
apk list --installed 2>/dev/null | grep -E '^(openjdk[0-9]+|ruby-[0-9]|ruby-libs-[0-9]|php[0-9]+-[0-9]|php[0-9]+-(cli|fpm|cgi|common)-[0-9])'
Reads the apk database.
2. Paste the output, or upload an SBOM
Command output, package lists, or CycloneDX / SPDX JSON (one or several files, up to 10 MB each).
Loading…
Sample report · illustrative data
Sample report: one Linux host and two container images
Made-up output from the Linux and Docker commands: a forgotten Temurin 17 under /opt, a patched Corretto 21, the OS Java 11, two Rubies, two PHPs and two images. 10 runtimes found.
| Where | Runtime | Version | Flaw | Status | Why |
|---|---|---|---|---|---|
| /opt/payments/jdk-17.0.13+11/bin/java | Java (Temurin)version command | 17.0.13 | Java4ShellCVE-2026-114938 | Affected | Below 17.0.21.1, the first fixed release on the Java 17 line.Caveat: Only exploitable on x86-64 CPUs with AVX-512 VBMI (Calif, Canadian Cyber Centre); Calif says ARM64 is not affected. Oracle does not mention CPU type, so patch anyway. |
| /usr/local/bin/ruby | Rubyversion command | 3.4.12 | Ruby2ShellCVE-2026-132825 | Affected | Below 3.4.13, the fixed 3.4 release. |
| /opt/legacy-portal/ruby/bin/ruby | Rubyversion command | 3.1.6p260 | Ruby2ShellCVE-2026-132825 | Affected | Ruby 3.1 is end of life and will not get the fix (ruby-lang.org); Veria Labs says the flaw has been present since 2.4.0. Upgrade to 3.3.14, 3.4.13 or 4.0.10. |
| /usr/local/bin/php | PHPversion command | 8.2.35 | phpAfterShellCVE-2026-126714 | Affected | Below 8.2.36. |
| registry.example.com/auth/login-api:5.2 | Javaimage setting | jdk-21.0.13+11 | Java4ShellCVE-2026-114938 | Affected | Below 21.0.13.1, the first fixed release on the Java 21 line.Caveat: Only exploitable on x86-64 CPUs with AVX-512 VBMI (Calif, Canadian Cyber Centre); Calif says ARM64 is not affected. Oracle does not mention CPU type, so patch anyway. |
| /usr/bin/php8.3 | PHPversion command | 8.3.6 | PHP2ShellCVE-2026-109618, CVE-2026-109619 · KEV | Unknown | Upstream 8.3 is fixed in 8.3.36; this flaw is in CISA KEV. Distribution packages may carry a backported fix under an older version number; confirm with your distribution's advisory. |
| /usr/bin/php8.3 | PHPversion command | 8.3.6 | phpAfterShellCVE-2026-126714 | Unknown | Upstream 8.3 is fixed in 8.3.37. Distribution packages may carry a backported fix under an older version number; confirm with your distribution's advisory. |
| dpkg packages | JavaOS package: openjdk-17-jre-headless | 17.0.21+9-1~deb12u1 | Java4ShellCVE-2026-114938 | Unknown | Same quarterly update as the fix (17.0.21), built by a distribution. Distribution packages may carry a backported fix under an older version number; confirm with your distribution's advisory.Caveat: Only exploitable on x86-64 CPUs with AVX-512 VBMI (Calif, Canadian Cyber Centre); Calif says ARM64 is not affected. Oracle does not mention CPU type, so patch anyway. |
| /opt/billing/jre/bin/java | Java (Corretto)version command | 21.0.13.1 | Java4ShellCVE-2026-114938 | Fixed | 21.0.13.1 or a vendor build of it. |
| /usr/local/bin/php | PHPversion command | 8.2.35 | PHP2ShellCVE-2026-109618, CVE-2026-109619 · KEV | Fixed | At or above 8.2.35. |
| registry.example.com/shop/web:2026.11 | PHPimage setting | 8.4.28 | PHP2ShellCVE-2026-109618, CVE-2026-109619 · KEV | Fixed | At or above 8.4.27. |
| registry.example.com/shop/web:2026.11 | PHPimage setting | 8.4.28 | phpAfterShellCVE-2026-126714 | Fixed | At or above 8.4.28. |
| /usr/lib/jvm/java-11-openjdk-amd64/bin/java | Java (Ubuntu)version command | 11.0.25 | Java4ShellCVE-2026-114938 | Not affected | Java 11 is not affected (OpenJDK advisory; Red Hat says OpenJDK 11 does not contain the code). |
Made-up example data. Your own run uses your inputs. Downloads of the full report need Pro.
TL;DRWhat this tool is
5 points
- Pick where to look (Linux host, Windows host, Docker images, Kubernetes) and copy read-only commands that list every java, ruby and php binary, JDK release file, OS package and container image runtime.
- Paste the output, or upload CycloneDX or SPDX JSON SBOMs from Syft. Everything is parsed in your browser: nothing you paste is sent to PlayCISO.
- Each runtime gets a status per flaw: Java4Shell (CVE-2026-114938), Ruby2Shell (CVE-2026-132825), PHP2Shell (CVE-2026-109618 and CVE-2026-109619) and phpAfterShell (CVE-2026-126714): affected, fixed, not affected or unknown, with the reason.
- Fixed versions: Java 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1; Ruby 3.3.14, 3.4.13, 4.0.10; PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 (these also contain the PHP2Shell fix).
- Distribution packages are flagged when a backport could hide the fix behind an older version number, and Java rows carry the x86-64 AVX-512 VBMI condition as a caveat.
Why runtimes hide
Patching "Java" or "PHP" usually means updating the OS package. But vendors bundle their own Java in a jre folder, teams unpack JDKs under /opt, version managers keep old Rubies, and every container image carries its own runtime that the host update never touches. Three of this month's flaws are in the runtimes themselves, so every one of those copies needs the fix: updating an application or a gem does not help.
How each status is decided
- Affected: the version is in the affected range the vendor published.
- Fixed: at or above the first fixed release on that line.
- Not affected: outside the range, for example standard Java 8 and 11 for Java4Shell.
- Unknown: the version alone cannot tell, for example a distribution package that may carry a backport, an end-of-life line the advisory does not list, or a pre-release build. The reason says what to check.
After you patch: restart the services (a running JVM or PHP-FPM keeps the old code until it restarts), rebuild and redeploy container images, and ask vendors whose products bundle a runtime for their fixed build. PHP2Shell is exploited in the wild, so a server exposed before patching needs a compromise check too.
Frequently asked questions
How do I find every Java version installed on a Linux server?
Search the disk for java binaries and ask each one for its version: find / -xdev -name java -type f, then run <path> -version on each result. The tool gives you a one-line loop that does this for java, ruby and php together and labels each result with its path. To avoid running anything, read the release file in each JDK or JRE folder, which states JAVA_VERSION and IMPLEMENTOR, or list OS packages with dpkg-query, rpm -qa or apk. Copies bundled inside applications (a jre folder under /opt) only show up with the file search, which is why it is the first command.
Which Java versions are affected by Java4Shell (CVE-2026-114938)?
Pre-fix builds of Java 17, 21, 25 and 27. Oracle lists Java SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, the Java 8 Performance Pack build 8u511b33-perf, GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3 and GraalVM Enterprise Edition 21.3.20.0.3. Fixed releases are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and vendor builds of them such as Temurin and Corretto. Standard Java 8 and 11 are not affected, and Calif and Red Hat say the code arrived in 17.0.6. Only x86-64 CPUs with AVX-512 VBMI are exposed, but patch anyway.
Which Ruby versions fix Ruby2Shell (CVE-2026-132825)?
Ruby 3.3.14, 3.4.13 and 4.0.10, released on 18 November 2026. ruby-lang.org lists Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12 and 4.0.0 through 4.0.9 as affected, and says Ruby 3.2 and earlier are end of life and will not receive the fix. Updating Rails or Sinatra does not help: the bug is in the interpreter.
Which PHP versions fix PHP2Shell and phpAfterShell?
PHP2Shell (CVE-2026-109618 and CVE-2026-109619, in CISA KEV) is fixed in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. phpAfterShell (CVE-2026-126714) is fixed in 8.2.36, 8.3.37, 8.4.28 and 8.5.13, which also contain the PHP2Shell fix, so take those. PHP's phpAfterShell advisory covers every version below 8.2.36, and PHP 8.1 and older get no fix from the PHP project.
Why does the tool say "Unknown" for my Ubuntu, Debian or Red Hat package?
Distributions often fix a flaw by patching the version they already ship, so a package can be safe while its version number is below the upstream fix. The tool cannot see that from a version string, so it marks those rows Unknown and asks you to check the distribution's security tracker for the CVE. Runtimes built from upstream (official Docker images, Temurin, Corretto, a Ruby or PHP you compiled) are judged on the version alone.
Are the commands safe to run in production?
They only read: they list files and packages, read image settings and print version numbers. The file search runs each java, ruby or php binary it finds with its version flag and a 10-second timeout. One optional Docker command starts a short-lived container from each image with no network and without its entrypoint, and says so; the Syft SBOM option reads images without running them. Nothing is installed or changed. The output you paste is checked in your browser and is not sent to PlayCISO.
More security tools
The tools people use most on PlayCISO.
Catch injected instructions hiding in content your AI agent should only read.
Score your readiness against the first international standard for AI security threats.
Critical CVEs across 21 major vendors, month by month — and what the 2026 surge means.
Build an ordered ruleset, replay labelled packets and catch shadowed and any-to-any rules.
Self-assess all six Functions, from Govern to Recover, and see your weakest one.
Search 172 threat actors across Microsoft, CrowdStrike, Mandiant and community names.