Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Tomcat Vulnerable to Web Cache Poisoning

CVE-2005-2090GHSA-f2gq-p6qv-ccw4

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.apache.tomcat:tomcat

    Affected
    >= 5.0.0, <= 5.0.19>= 4.0.0, <= 4.1.24
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2005-2090: 26.11% estimated exploitation activity in the next 30 days; percentile 97.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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."

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-f2gq-p6qv-ccw4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2005-2090

Advisory: Tomcat Vulnerable to Web Cache Poisoning
IDs: CVE-2005-2090, GHSA-f2gq-p6qv-ccw4
Record: https://patchnext.com/advisories/cve-2005-2090 (revision 1, source checked 26 Oct 2026, 16:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.tomcat:tomcat: affected >= 5.0.0, <= 5.0.19; >= 4.0.0, <= 4.1.24

## Suggested inspection (read-only)
- Maven org.apache.tomcat:tomcat: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.tomcat:tomcat.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f2gq-p6qv-ccw4 (GitHub-reviewed advisory GHSA-f2gq-p6qv-ccw4 lists affected ranges: Maven org.apache.tomcat:tomcat >=5.0.0 =4.0.0 <=4.1.24)

Commands are suggestions: review each one before running it.

Loading voting…