How severe is CVE-2009-0580?

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

Which packages are affected by CVE-2009-0580?

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

How do I fix CVE-2009-0580?

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

How do I detect CVE-2009-0580 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-2009-0580 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2009-0580 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2009-0580, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation 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-2009-0580?

CVE-2009-0580 has an EPSS (Exploit Prediction Scoring System) score of 94.4%, placing it in the 100th 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-2009-0580?

CVE-2009-0580 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2009-0580 published, and has it been updated?

CVE-2009-0580 was published on May 2, 2022 and was last updated on November 8, 2023. 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-2009-0580 — tomcat

CVE-2009-0580 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Exposure of Sensitive Information in Apache Tomcat

Published

May 2, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

94.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

☕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

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when FORM authentication is used, allows remote attackers to enumerate valid usernames via requests to /j_security_check with malformed URL encoding of passwords, related to improper error checking in the (1) MemoryRealm, (2) DataSourceRealm, and (3) JDBCRealm authentication realms, as demonstrated by a % (percent) value for the j_password parameter.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.1.0&&< 4.1.40	4.1.40`org.apache.tomcat:tomcat:4.1.40`
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.0.0&&< 5.5.28	5.5.28`org.apache.tomcat:tomcat:5.5.28`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.19	6.0.19`org.apache.tomcat:tomcat:6.0.19`

Affected Products

1 product · 87 configurations

Application

tomcatapache

85 versions

4.1.04.1.14.1.24.1.34.1.44.1.54.1.64.1.74.1.84.1.94.1.104.1.11

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-33023remotemultiple✓ Verified

Apache Tomcat 6.0.18 - Form Authentication Existing/Non-Existing 'Username' Enumeration

by D. Matscheko · Jun 3, 2009

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.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-0580 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

Product	Fixed in	Advisory
JBEAP 4.2.0 for RHEL 4	`hibernate3-1:3.2.4-1.SP1_CP08.0jpp.ep1.2.el4`	RHSA-2009:1144
JBEAP 4.2.0 for RHEL 5	`hibernate3-1:3.2.4-1.SP1_CP08.0jpp.ep1.2.3.el5`	RHSA-2009:1143
JBEWS 1.0 for RHEL 4	`tomcat5-0:5.5.23-1.patch07.19.ep5.el4`	RHSA-2009:1454
JBEWS 1.0 for RHEL 4	`tomcat6-0:6.0.18-11.3.ep5.el4`	RHSA-2009:1506
Red Hat Certificate System 7.3	`ant-0:1.6.5-1jpp_1rh`	RHSA-2010:0602
Red Hat Developer Suite V.3	`tomcat5-0:5.5.23-0jpp_18rh`	RHSA-2009:1563
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.7.el5_3.2`	RHSA-2009:1164
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4	`glassfish-jaxb-0:2.1.4-1.11.ep1.el4`	RHSA-2009:1146

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-0580 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works