How severe is CVE-2002-2006?

No CVSS score has been assigned to CVE-2002-2006 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2002-2006?

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

How do I fix CVE-2002-2006?

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

How do I detect CVE-2002-2006 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-2002-2006 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.

Is CVE-2002-2006 actively exploited in the wild?

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

CVE-2002-2006 has an EPSS (Exploit Prediction Scoring System) score of 30.7%, placing it in the 98th 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.

When was CVE-2002-2006 published, and has it been updated?

CVE-2002-2006 was published on April 30, 2022 and was last updated on February 12, 2024. 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

CVE-2002-2006 — tomcat

CVE-2002-2006 is a security vulnerability in org.apache.tomcat:tomcat. 3 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.

Apache Tomcat Default Installation Reveals Sensitive Information

Published

Apr 30, 2022

Updated

Feb 12, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

30.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕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 default installation of Apache Tomcat 4.0 through 4.1 and 3.0 through 3.3.1 allows remote attackers to obtain the installation path and other sensitive system information via the (1) SnoopServlet or (2) TroubleShooter example servlets.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.0.0&&< 4.1.0	4.1.0`org.apache.tomcat:tomcat:4.1.0`
☕Maven	`org.apache.tomcat:tomcat`	≥ 3.0&&< 3.3a	3.3a`org.apache.tomcat:tomcat:3.3a`

Affected Products

1 product · 14 configurations

Application

tomcatapache

14 versions

3.03.13.1.13.23.2.13.2.33.2.43.33.3.14.0.04.0.14.0.2

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-21412remoteunix✓ Verified

Apache Tomcat 4.0/4.1 - Servlet Full Path Disclosure

by CHINANSL Security Team · Apr 23, 2002

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 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-2006 is resolved across your whole dependency graph.
Workarounds
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2002-2006 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works