CVE-2009-0580

NONECVSS 0.09.0
EchelonGraph scoreLOW confidence

Score elevated to 9.0 because EPSS predicts 88% probability of exploitation within the next 30 days (top 0.5% of all CVEs). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss
Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 59 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 94%
CISA-KEV: Not listedEPSS: 94%CVSS: Exploit: NoneExposed: 59

A fix is available — apply it.

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.

Live · internet exposure

59 internet-exposed hosts are running an affected version of CVE-2009-0580 right now.

across 20 countries (China, United States, United Kingdom, Singapore, Indonesia)top: tomcat
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
EG Score
9.0(low)
EPSS
99.8%
KEV
Not listed

Published

June 5, 2009

Last Modified

April 23, 2026

Vendor Advisories for CVE-2009-0580(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat6-examples (6.0.18-0ubuntu6.1) @ jaunty2026-05-30ubuntu
redhatxml-commons-0:1.3.02-2jpp_1rh2010-08-04redhat
redhattomcat5-0:5.5.23-0jpp_18rh2009-11-30redhat
redhattomcat5-0:5.5.23-0jpp_4rh.162009-11-09redhat
redhattomcat6-0:6.0.18-12.0.ep5.el52009-10-14redhat
redhattomcat5-0:5.5.23-0jpp.9.6.ep5.el52009-09-21redhat
redhattomcat5-0:5.5.23-0jpp.7.el5_3.22009-07-21redhat
redhatxerces-j2-0:2.7.1-9jpp.ep1.2.el42009-07-06redhat
redhatrh-eap-docs-0:4.3.0-5.GA_CP05.ep1.2.1.el52009-07-06redhat
redhatrh-eap-docs-0:4.2.0-5.GA_CP07.ep1.1.1.el52009-07-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat:tomcat6.0.19

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 1× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-01 15:02 UTCEPSS rescore
  2. 2026-06-30 23:19 UTCEPSS rescore
  3. 2026-06-25 13:46 UTCEPSS rescore
  4. 2026-06-25 13:46 UTCEPSS rescore
  5. 2026-06-23 21:29 UTCEPSS rescore
  6. 2026-06-23 21:29 UTCEPSS rescore
  7. 2026-06-18 17:49 UTCEPSS rescore
  8. 2026-06-18 17:49 UTCEPSS rescore
  9. 2026-06-15 17:44 UTCEPSS rescore
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-14 23:14 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-10 22:14 UTCEPSS rescore
  14. 2026-06-10 13:17 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-07 15:22 UTCEPSS rescore
  17. 2026-06-06 13:44 UTCEPSS rescore
  18. 2026-06-06 13:44 UTCEPSS rescore
  19. 2026-06-06 13:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 06:07 UTCEPSS rescore
  23. 2026-05-30 16:39 UTCEG score recompute
  24. 2026-05-30 16:39 UTCVendor advisory
  25. 2026-05-29 13:40 UTCEPSS rescore
Show 13 more
  1. 2026-05-28 13:42 UTCEPSS rescore
  2. 2026-05-28 13:42 UTCEPSS rescore
  3. 2026-05-28 13:42 UTCEPSS rescore
  4. 2026-05-26 13:41 UTCEPSS rescore
  5. 2026-05-26 13:41 UTCEPSS rescore
  6. 2026-05-26 07:16 UTCEPSS rescore
  7. 2026-05-26 07:16 UTCEPSS rescore
  8. 2026-05-24 16:43 UTCEPSS rescore
  9. 2026-05-22 21:15 UTCEPSS rescore
  10. 2026-05-22 21:15 UTCEPSS rescore
  11. 2026-05-20 22:37 UTCEPSS rescore
  12. 2026-05-20 22:37 UTCEPSS rescore
  13. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-33023✓ verified
    First seen Jun 3, 2009

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

    Open source ↗
  • Metasploitauxiliary/scanner/http/tomcat_enum✓ verified
    First seen Jan 1, 2009

    Apache Tomcat User Enumeration

    Open source ↗

Frequently asked(4)

What is CVE-2009-0580?
CVE-2009-0580 is a none vulnerability published on June 5, 2009. 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 /jsecuritycheck with malformed URL encoding of passwords, related to improper error checking in the (1)…
When was CVE-2009-0580 disclosed?
CVE-2009-0580 was first published in the National Vulnerability Database on June 5, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-0580 actively exploited?
CVE-2009-0580 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-0580?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-0580, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-0580

Explore →

Is Your Infrastructure Affected by CVE-2009-0580?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.