CVE-2005-2090

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:N/I:P/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 29.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Elevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 30%CVSS v2: 4.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling."

CVSS v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3(low)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
30%
EPSS %ILE
98%
KEV
Not listed

Published

July 5, 2005

Last Modified

April 16, 2026

References (98)

Vendor Advisories for CVE-2005-2090(1)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatxml-commons-0:1.3.02-2jpp_1rh2010-08-04redhat
redhattomcat5-0:5.0.30-0jpp_10rh2008-06-30redhat
redhattyrex-0:1.0.1-2jpp_2rh2007-11-26redhat
redhattomcat5-0:5.5.23-0jpp_6rh2007-05-24redhat
redhatjbossas-0:4.0.5-2.CP04.el4s1.22007-05-24redhat
redhattomcat5-0:5.5.23-0jpp_4rh.32007-05-21redhat
redhattomcat5-0:5.5.23-0jpp.1.0.3.el52007-05-14redhat
redhattomcat5-0:5.0.30-0jpp_5rh2007-05-08redhat
mavenorg.apache.tomcat:tomcat—ghsa

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:tomcat———

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× 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-26 13:26 UTCEG score recompute▲ 4.30
  2. 2026-07-25 14:11 UTCEPSS rescore
  3. 2026-07-24 14:11 UTCEPSS rescore
  4. 2026-07-23 00:48 UTCEG score recompute
  5. 2026-07-23 00:28 UTCEG score recompute
  6. 2026-07-22 23:52 UTCEG score recompute
  7. 2026-07-22 21:32 UTCEG score recompute
  8. 2026-07-18 09:59 UTCEPSS rescore
  9. 2026-07-18 09:59 UTCEPSS rescore
  10. 2026-07-15 16:53 UTCEPSS rescore
  11. 2026-07-15 01:55 UTCEPSS rescore
  12. 2026-07-15 01:55 UTCEPSS rescore
  13. 2026-07-13 22:24 UTCEPSS rescore
  14. 2026-07-13 06:07 UTCEPSS rescore
  15. 2026-07-13 06:07 UTCEPSS rescore
  16. 2026-07-11 08:22 UTCEPSS rescore
  17. 2026-07-11 08:22 UTCEPSS rescore
  18. 2026-07-08 15:09 UTCEPSS rescore
  19. 2026-07-02 14:00 UTCEPSS rescore
  20. 2026-07-01 15:01 UTCEPSS rescore
  21. 2026-06-29 14:02 UTCEPSS rescore
  22. 2026-06-29 14:02 UTCEPSS rescore
  23. 2026-06-28 04:52 UTCEPSS rescore
  24. 2026-06-27 03:04 UTCEPSS rescore
  25. 2026-06-25 13:46 UTCEPSS rescore
Show 44 more
  1. 2026-06-24 14:01 UTCEPSS rescore
  2. 2026-06-23 21:29 UTCEPSS rescore
  3. 2026-06-21 01:56 UTCEPSS rescore
  4. 2026-06-19 19:22 UTCEPSS rescore
  5. 2026-06-18 17:49 UTCEPSS rescore
  6. 2026-06-18 17:49 UTCEPSS rescore
  7. 2026-06-17 17:49 UTCEPSS rescore
  8. 2026-06-17 17:49 UTCEPSS rescore
  9. 2026-06-16 17:49 UTCEPSS rescore
  10. 2026-06-16 17:49 UTCEPSS rescore
  11. 2026-06-15 17:44 UTCEPSS rescore
  12. 2026-06-14 23:13 UTCEPSS rescore
  13. 2026-06-14 23:13 UTCEPSS rescore
  14. 2026-06-13 22:56 UTCEPSS rescore
  15. 2026-06-12 23:08 UTCEPSS rescore
  16. 2026-06-11 13:55 UTCEPSS rescore
  17. 2026-06-10 22:14 UTCEPSS rescore
  18. 2026-06-08 14:13 UTCEPSS rescore
  19. 2026-06-05 22:43 UTCEPSS rescore
  20. 2026-06-05 22:43 UTCEPSS rescore
  21. 2026-06-05 06:07 UTCEPSS rescore
  22. 2026-06-05 06:07 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-05-31 12:47 UTCEG score recompute
  28. 2026-05-31 12:47 UTCVendor advisory
  29. 2026-05-31 12:47 UTCGHSA enrichment
  30. 2026-05-31 00:13 UTCEPSS rescore
  31. 2026-05-31 00:13 UTCEPSS rescore
  32. 2026-05-29 13:40 UTCEPSS rescore
  33. 2026-05-29 13:40 UTCEPSS rescore
  34. 2026-05-27 13:37 UTCEPSS rescore
  35. 2026-05-26 13:41 UTCEPSS rescore
  36. 2026-05-26 13:41 UTCEPSS rescore
  37. 2026-05-26 07:16 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-24 16:42 UTCEPSS rescore
  40. 2026-05-22 21:15 UTCEPSS rescore
  41. 2026-05-21 22:38 UTCEPSS rescore
  42. 2026-05-20 22:36 UTCEPSS rescore
  43. 2026-05-20 22:36 UTCEPSS rescore
  44. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2005-2090?
CVE-2005-2090 is a medium vulnerability published on July 5, 2005. Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat…
When was CVE-2005-2090 disclosed?
CVE-2005-2090 was first published in the National Vulnerability Database on July 5, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-2090 actively exploited?
CVE-2005-2090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30% probability of exploitation in the next 30 days, which ranks it in the top 2.0% of all scored CVEs.
How do I remediate CVE-2005-2090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2090, 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-2005-2090

Explore →

Is Your Infrastructure Affected by CVE-2005-2090?

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

Start Free Scan →Browse All CVEs