How severe is CVE-2017-5647?

CVE-2017-5647 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-5647?

CVE-2017-5647 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-5647?

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

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

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

How do I mitigate CVE-2017-5647 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.

How does O3 Security protect against CVE-2017-5647?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2017-5647 can be triaged on real exposure rather than presence alone.

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

No public exploit code has been indexed for CVE-2017-5647 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-5647?

CVE-2017-5647 has an EPSS (Exploit Prediction Scoring System) score of 16.8%, placing it in the 97th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2017-5647?

CVE-2017-5647 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2017-5647 was published on April 17, 2017 and was last updated on July 8, 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

HIGH severity

CVE-2017-5647 — tomcat

HIGH

CVE-2017-5647 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 16.8% (97th percentile). A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Also known asGHSA-3gv7-3h64-78cm

Published

Apr 17, 2017

Updated

Jul 8, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

16.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2017-5647 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M1&&< 9.0.0.M19	9.0.0.M19`org.apache.tomcat:tomcat:9.0.0.M19`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.0&&< 8.5.13	8.5.13`org.apache.tomcat:tomcat:8.5.13`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0&&< 8.0.43	8.0.43`org.apache.tomcat:tomcat:8.0.43`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.77	7.0.77`org.apache.tomcat:tomcat:7.0.77`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.53	6.0.53`org.apache.tomcat:tomcat:6.0.53`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 9.0.0.M19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-5647 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2017-5647 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2017-5647. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-111.el6_9`	RHSA-2017:3080
Red Hat Enterprise Linux 7	`tomcat-0:7.0.76-3.el7_4`	RHSA-2017:3081
Red Hat JBoss Enterprise Web Server 2 for RHEL 6	`jbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el6`	RHSA-2017:2493
Red Hat JBoss Web Server 2.1	`tomcat6`	RHSA-2017:2494
Red Hat JBoss Web Server 3.1	see advisory	RHSA-2017:1802
Red Hat JBoss Web Server 3 for RHEL 6	`log4j-eap6-0:1.2.16-12.redhat_3.1.ep6.el6`	RHSA-2017:1801

UbuntuHIGH

USN-3519-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-5647 in your dependencies?

O3 Security finds CVE-2017-5647 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works