How severe is CVE-2024-50379?

CVE-2024-50379 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-50379?

CVE-2024-50379 affects the following packages: org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-50379?

Update org.apache.tomcat:tomcat-catalina to 11.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-50379 is resolved across your whole dependency graph.

How do I detect CVE-2024-50379 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-catalina, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-50379 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-50379?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-50379 can be triaged on real exposure rather than presence alone.

Is CVE-2024-50379 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2024-50379, including 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-50379?

CVE-2024-50379 has an EPSS (Exploit Prediction Scoring System) score of 44.3%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2024-50379?

CVE-2024-50379 is classified as CWE-367 (CWE-367). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-50379 published, and has it been updated?

CVE-2024-50379 was published on December 17, 2024 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2024-50379 — tomcat-catalina

CRITICAL

CVE-2024-50379 is a critical-severity (CVSS 9.8) CWE-367 vulnerability in org.apache.tomcat:tomcat-catalina. 10 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat-catalina — see the affected versions and patch details below.

Apache Tomcat: RCE due to TOCTOU issue in JSP compilation

Also known asBIT-tomcat-2024-50379GHSA-5j33-cvvr-w245

Published

Dec 17, 2024

Updated

Aug 12, 2026

Affected

8 pkgs

Patched

6 / 8

Exploits

10 known

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-50379.

EPSS Exploitation Probability

via FIRST.org ↗

44.3%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-50379 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

8 pkgs affected

☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat.embed:tomcat-embed-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.1, from 10.1.0-M1 through 10.1.33, from 9.0.0.M1 through 9.0.97.

The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.2, 10.1.34 or 9.0.98, which fixes the issue.

Affected Packages

8 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat-catalina`	≥ 11.0.0-M1&&< 11.0.2	11.0.2`org.apache.tomcat:tomcat-catalina:11.0.2`
☕Maven	`org.apache.tomcat:tomcat-catalina`	≥ 10.1.0-M1&&< 10.1.34	10.1.34`org.apache.tomcat:tomcat-catalina:10.1.34`
☕Maven	`org.apache.tomcat:tomcat-catalina`	≥ 9.0.0.M1&&< 9.0.98	9.0.98`org.apache.tomcat:tomcat-catalina:9.0.98`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 11.0.0-M1&&< 11.0.2	11.0.2`org.apache.tomcat.embed:tomcat-embed-core:11.0.2`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 10.1.0-M1&&< 10.1.34	10.1.34`org.apache.tomcat.embed:tomcat-embed-core:10.1.34`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 9.0.0.M1&&< 9.0.98	9.0.98`org.apache.tomcat.embed:tomcat-embed-core:9.0.98`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.