How severe is CVE-2017-5651?

CVE-2017-5651 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-5651?

CVE-2017-5651 affects the following packages: org.apache.tomcat:tomcat-coyote (Maven), org.apache.tomcat:tomcat-coyote (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-5651?

Update org.apache.tomcat:tomcat-coyote to 9.0.0.M19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5651 is resolved across your whole dependency graph.

How do I detect CVE-2017-5651 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-coyote, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-5651 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-5651 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-5651 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-5651?

CVE-2017-5651 has an EPSS (Exploit Prediction Scoring System) score of 7.8%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2017-5651 published, and has it been updated?

CVE-2017-5651 was published on April 17, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2017-5651 — tomcat-coyote

CRITICALFix: apache/tomcat@494429c

CVE-2017-5651 is a critical-severity (CVSS 9.8) vulnerability in org.apache.tomcat:tomcat-coyote. A fix is available for org.apache.tomcat:tomcat-coyote — see the affected versions and patch details below.

Expected Behavior Violation in Apache Tomcat

Also known asGHSA-9hg2-395j-83rm

Published

Apr 17, 2017

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the refactoring of the HTTP connectors introduced a regression in the send file processing. If the send file processing completed quickly, it was possible for the Processor to be added to the processor cache twice. This could result in the same Processor being used for multiple requests which in turn could lead to unexpected errors and/or response mix-up.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 9.0.0.M1&&< 9.0.0.M19	9.0.0.M19`org.apache.tomcat:tomcat-coyote:9.0.0.M19`
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 8.5.0&&< 8.5.13	8.5.13`org.apache.tomcat:tomcat-coyote:8.5.13`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 9.0.0.M1&&< 9.0.0.M19	9.0.0.M19`org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M19`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 8.5.0&&< 8.5.13	8.5.13`org.apache.tomcat.embed:tomcat-embed-core:8.5.13`

Affected Products

1 product · 31 configurations

Application

tomcatapache

14 versions

8.5.08.5.18.5.28.5.38.5.48.5.58.5.68.5.78.5.88.5.98.5.108.5.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-coyote, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat-coyote to 9.0.0.M19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5651 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-5651 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works