How severe is CVE-2022-29885?

CVE-2022-29885 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-29885?

CVE-2022-29885 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-29885?

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

How do I detect CVE-2022-29885 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-29885 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2022-29885, including 1 documented proof-of-concept exploit on Exploit-DB and 3 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-2022-29885?

CVE-2022-29885 has an EPSS (Exploit Prediction Scoring System) score of 73.5%, 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2022-29885?

CVE-2022-29885 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-29885 published, and has it been updated?

CVE-2022-29885 was published on May 12, 2022 and was last updated on October 28, 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

HIGH severity

CVE-2022-29885 — tomcat

HIGHFix: apache/tomcat@0fa7721

CVE-2022-29885 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.apache.tomcat:tomcat. 6 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

EncryptInterceptor does not provide complete protection on insecure networks

Also known asBIT-tomcat-2022-29885GHSA-r84p-88g2-2vx2

Published

May 12, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

6 known

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

EPSS Exploitation Probability

via FIRST.org ↗

73.5%probability of exploitation in next 30 days

Very High Risk0.00%

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

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

The documentation of Apache Tomcat 10.1.0-M1 to 10.1.0-M14, 10.0.0-M1 to 10.0.20, 9.0.13 to 9.0.62 and 8.5.38 to 8.5.78 for the EncryptInterceptor incorrectly stated it enabled Tomcat clustering to run over an untrusted network. This was not correct. While the EncryptInterceptor does provide confidentiality and integrity protection, it does not protect against all risks associated with running over any untrusted network, particularly DoS risks.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.1.0-M1&&< 10.1.0-M15	10.1.0-M15`org.apache.tomcat:tomcat:10.1.0-M15`
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.0.0-M1&&< 10.0.21	10.0.21`org.apache.tomcat:tomcat:10.0.21`
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.13&&< 9.0.63	9.0.63`org.apache.tomcat:tomcat:9.0.63`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.38&&< 8.5.79	8.5.79`org.apache.tomcat:tomcat:8.5.79`

Affected Products

3 products · 20 configurations

Application

tomcatapache

≥ 10.0.0 && ≤ 10.0.20

1 version

10.1.0

debian linuxdebian

2 versions

10.011.0

Application

hospitality cruise shipboard property management systemoracle

1 version

20.2.1

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.

EDB-51262dosmultiple

Apache Tomcat 10.1 - Denial Of Service

by Cristian Giustini · Apr 5, 2023

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 10.1.0-M15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29885 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

This flaw describes a mistake made in the documentation which overstated the protection provided by the clustering feature. As the impact is Low and a patch would not directly improve the security posture of Apache Tomcat, this flaw is marked as will not fix for all Red Hat products. This may be fixed in a future…

Workaround published by Red Hat

For customers who use clustering on an untrusted network and require full protection, an alternate solution is recommended such as using a VPN.

Source: Red Hat security advisory for CVE-2022-29885 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-29885 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works