CVE-2024-50379: Apache Tomcat JSP Compilation TOCTOU Remote Code Execution
- Vendors
- NetAppApache Software Foundation
CVE-2024-50379 is a time-of-check time-of-use race condition during JSP compilation in Apache Tomcat. On case-insensitive file systems, a remote unauthenticated attacker can exploit specially crafted file uploads to achieve remote code execution when the Default servlet is configured to permit writes, a non-default setting. Affected releases are 11.0.0-M1 through 11.0.1, 10.1.0-M1 through 10.1.33, and 9.0.0.M1 through 9.0.97. End-of-life releases 8.5.0 through 8.5.100 are also affected; older unsupported releases may be affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution with the privileges of the Tomcat process, potentially compromising the confidentiality, integrity, and availability of the application and resources accessible to that process. Consequences can include disclosure or modification of application data and disruption of hosted services. Operating-system-level access is constrained by the Tomcat service account's privileges.
Mitigation
If you can’t patch tonight, do this now.
Disable writes through the Default servlet by restoring its read-only configuration, readonly=true. This removes a required exploitation condition. If write-enabled operation on a case-insensitive file system must continue after applying the initial Tomcat fix, also address the related canonical-path caching issue: set sun.io.useCanonCaches=false on Java 8 and Java 11; on Java 17, ensure the property is false if explicitly configured. Java 21 and later do not require this property because the problematic cache was removed. Cache configuration alone should not replace the Tomcat update.
Remediation
Patch, then assume compromise.
Upgrade Apache Tomcat to at least 11.0.2, 10.1.34, or 9.0.98 in the corresponding release branch, preferably to a current supported release. Migrate affected Tomcat 8.5 installations to a supported, fixed branch. For products embedding Tomcat, install the applicable vendor update. Account for the incomplete mitigation tracked as CVE-2024-56337: affected Java configurations also require appropriate canonical-path cache settings. Tomcat 11.0.3, 10.1.35, and 9.0.99 onward add checks for these settings before permitting write-enabled Default servlet operation on case-insensitive file systems.
Exploits
12 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2024-50379 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2024-50379 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2024-50379?
- Yes. Mallory tracks 12 public exploits or proofs of concept for CVE-2024-50379, the earliest disclosed Dec 18, 2024.
- Is there a patch for CVE-2024-50379?
- Upgrade Apache Tomcat to at least 11.0.2, 10.1.34, or 9.0.98 in the corresponding release branch, preferably to a current supported release. Migrate affected Tomcat 8.5 installations to a supported, fixed branch.
- What products are affected by CVE-2024-50379?
- Apache Software Foundation Tomcat and NetApp Bootstrap Os.
- How severe is CVE-2024-50379?
- CVE-2024-50379 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 42.7% (99th percentile) as of Nov 16, 2026.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.