Publicly Disclosed Critical RCE CVEs: CrowdStrike Research and Guidance
Uncover exposure, monitor for post-exploit activity, and accelerate remediation of Java4Shell and NGINX2Root with CrowdStrike research and guidance.
Get expert analysis, technical findings, and guidance for your next steps.
- Java4Shell
- NGINX2Root
- PHP2Shell
Frequently Asked Questions
Only x86-64 processors that support AVX-512 VBMI are affected (Intel Ice Lake and newer, AMD Zen 4 and newer). ARM64 and i386 systems are not affected.
Branch | Affected versions | Fixed version |
Java 17 | 17.0.6 through 17.0.21 | 17.0.21.1 |
Java 21 | Up to 21.0.13 | 21.0.13.1 |
Java 25 | Up to 25.0.5 | 25.0.5.1 |
Java 27 | Up to 27.0.1 | 27.0.1.1 |
Oracle Java 8 Performance Pack | 8u511b33-perf | See Oracle advisory |
Standard Java 8 and Java 11 environments are not affected; the Oracle Java 8 Performance Pack is the exception. Downstream distributions are also affected, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, Oracle GraalVM, BellSoft Liberica, and SAP SapMachine. Applications that bundle their own Java runtime, container images, and managed cloud services can be affected as well.
Falcon Exposure Management uses sensor-based assessment to identify Java runtimes affected by CVE-2026-114938 on supported Windows, Linux, and macOS hosts. Coverage includes Oracle Java SE, OpenJDK, and downstream distributions such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, Oracle GraalVM, BellSoft Liberica, and SAP SapMachine. Hosts updated to 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1 are no longer flagged.
Standard install checks work on all supported sensor versions. Additional checks find custom or bundled installs: a system-wide Java check on Windows (sensor 7.40 or later, with "Enable Full System Visibility" turned on, C: drive only) and a running-process check on Linux (sensor 7.31 or later). On Linux, Exposure Management also checks whether AVX-512 VBMI is enabled. On Windows and macOS it may flag hosts that are not exploitable, so prioritize systems with supported processors.
Falcon Exposure Management and Falcon Spotlight customers can find exposed hosts in the Falcon console under Exposure Management > Vulnerability Management > Vulnerabilities. For containers, Falcon Cloud Security image assessment identifies images carrying an affected runtime and shows which are running. Falcon Cloud Security Cloud Risk flags internet-exposed instances running an affected Java version.
Patch systems that meet all three conditions immediately, starting with internet-facing Java services. Apply the November 2026 fixes from Oracle and OpenJDK or the equivalent update from your Java vendor. Then:
Restart all running JVMs. Upgrading the runtime on disk does not protect processes that are already running.
Rebuild container images on patched base images and redeploy them.
Inventory embedded runtimes in appliances and third-party applications, and check vendor advisories and the CISA alert on CVE-2026-114938.
Falcon for IT Application Management can deploy Java updates at scale for runtimes available in its Application Catalog. If a runtime is missing, update it with the vendor's installer through a Falcon for IT custom task or existing deployment tooling. It can take up to 24 hours for hosts to report on newly managed applications.
Frequently Asked Questions
How does CrowdStrike help organizations address NGINX2Root?
The CrowdStrike Falcon platform helps organizations identify vulnerable systems, prioritize remediation, and detect suspicious post-exploitation activity.
Falcon Exposure Management: Identifies affected nginx installations through host-based vulnerability assessment, network scanning, and EASM.
Falcon Cloud Security: Identifies vulnerable container images and affected running containers.
Falcon for IT: Provides inventory, exposure assessment, and Linux remediation workflows through a dedicated NGINX2Root content pack.
Falcon Endpoint Security: Detects suspicious post-exploitation behaviors, including malicious processes, web shells, and credential access.
Frequently Asked Questions
PHP2Shell comprises two new vulnerabilities, CVE-2026-109618 and CVE-2026-109619.
These vulnerabilities are not a bypass of CVE-2024-4577. They do not share the same root cause or execution code path, meaning that patching CVE-2024-4577 does not address PHP2Shell.
CrowdStrike experts recommend reviewing the published PHP2Shell technical research for illustrated process-tree behavior and examples of detection and prevention activity.
Organizations should use the published technical research and available security telemetry to guide their investigations.
Falcon Next-Gen SIEM provides PHP-related hunting content in the Emerging Threat Response dashboard, accessible through Log Management > Dashboards. Available investigations depend on the telemetry ingested and the detection content deployed.
A Falcon Next-Gen SIEM correlation template is available under the name “Generic - Web - PHP Memory Exhaustion During Request Startup (CVE-2026-109618 & CVE-2026-109619).” Its effectiveness depends on relevant log sources, field mappings, and configuration. Support for a particular web-server deployment, including IIS with FastCGI, should be confirmed against the current content documentation.