Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Apache Tomcat is vulnerable to HTTP request-smuggling

CVE-2013-4286GHSA-j448-j653-r3vj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.tomcat:tomcat 8.0.0-RC3, 7.0.47, 6.0.39), redeploy, then verify what is actually installed.

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
    < 6.0.39>= 7.0.0, < 7.0.47>= 8.0.0-RC1, < 8.0.0-RC3
    Fixed in
    8.0.0-RC3, 6.0.39, 7.0.47

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2013-4286: 16.21% estimated exploitation activity in the next 30 days; percentile 96.95 (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.

Apache Tomcat before 6.0.39, 7.x before 7.0.47, and 8.x before 8.0.0-RC3, when an HTTP connector or AJP connector is used, does not properly handle certain inconsistent HTTP request headers, which allows remote attackers to trigger incorrect identification of a request's length and conduct request-smuggling attacks via (1) multiple Content-Length headers or (2) a Content-Length header and a "Transfer-Encoding: chunked" header. NOTE: this vulnerability exists because of an incomplete fix for CVE-2005-2090.

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

    Published from ghsa record GHSA-j448-j653-r3vj

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-2013-4286

Advisory: Apache Tomcat is vulnerable to HTTP request-smuggling
IDs: CVE-2013-4286, GHSA-j448-j653-r3vj
Record: https://patchnext.com/advisories/cve-2013-4286 (revision 1, source checked 26 Oct 2026, 16:26 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 fix available; fixed versions by package: org.apache.tomcat:tomcat 8.0.0-RC3, 7.0.47, 6.0.39. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.tomcat:tomcat: affected < 6.0.39; >= 7.0.0, < 7.0.47; >= 8.0.0-RC1, < 8.0.0-RC3; fixed in 8.0.0-RC3, 6.0.39, 7.0.47

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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-j448-j653-r3vj (GitHub-reviewed advisory GHSA-j448-j653-r3vj lists affected ranges: Maven org.apache.tomcat:tomcat >=0 =7.0.0 =8.0.0-RC1 <8.0.0-RC3)

Commands are suggestions: review each one before running it.

Loading voting…