CVE-2013-4286

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 17%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
96.7%
KEV
Not listed

Published

February 26, 2014

Last Modified

April 29, 2026

References (90)

Vendor Advisories for CVE-2013-4286(1)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibtomcat7-java (7.0.42-1ubuntu0.1) @ saucy2026-05-28ubuntu
redhatjbossweb2015-05-14redhat
redhattomcat-0:7.0.42-5.el7_02014-06-10redhat
redhattomcat72014-05-21redhat
redhattomcat6-0:6.0.37-27_patch_04.ep6.el62014-05-21redhat
redhattomcat7-0:7.0.40-9_patch_02.ep6.el62014-05-21redhat
redhattomcat62014-05-21redhat
redhatpatch2014-05-15redhat
redhattomcat6-0:6.0.24-64.el6_52014-04-23redhat
redhatjbossweb-0:7.3.1-1.Final_redhat_1.1.ep6.el52014-03-31redhat
redhatjbossweb-0:7.3.1-1.Final_redhat_1.1.ep6.el62014-03-31redhat

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:tomcat8.0.0-RC18.0.0-RC3—

Additional Vendor Advisories

(15)

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

Frequently asked(4)

What is CVE-2013-4286?
CVE-2013-4286 is a none vulnerability published on February 26, 2014. 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…
When was CVE-2013-4286 disclosed?
CVE-2013-4286 was first published in the National Vulnerability Database on February 26, 2014, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-4286 actively exploited?
CVE-2013-4286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-4286?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-4286, 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-2013-4286

Explore →

Is Your Infrastructure Affected by CVE-2013-4286?

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

Start Free Scan →Browse All CVEs