Skip to content
Noroxi
CVE-2017-5647· NVD / CVE Program· CNA apache

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

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.

HighCVSS 7.5 · v3.0—No exploit Fix available
Published
Apr 17, 2017
Updated
Jun 16, 2026
EPSS
16.8% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 16.8%

Affected systems

VendorProduct
apachetomcat

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache tomcat6.0.0
  • apache tomcat6.0.1
  • apache tomcat6.0.10
  • apache tomcat6.0.11
  • apache tomcat6.0.12
  • apache tomcat6.0.13
  • apache tomcat6.0.14
  • apache tomcat6.0.15
  • apache tomcat6.0.16
  • apache tomcat6.0.17
  • apache tomcat6.0.18
  • apache tomcat6.0.19
  • apache tomcat6.0.2
  • apache tomcat6.0.20
  • apache tomcat6.0.21
  • apache tomcat6.0.22
  • apache tomcat6.0.23
  • apache tomcat6.0.24
  • apache tomcat6.0.25
  • apache tomcat6.0.26

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation 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, 6.0.0 to 6.0.52affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:7tomcat7before 7.0.28-4+deb7u127.0.28-4+deb7u12
Debian:8tomcat7before 7.0.56-3+deb8u107.0.56-3+deb8u10
Debian:8tomcat8before 8.0.14-1+deb8u98.0.14-1+deb8u9
Mavenorg.apache.tomcat:tomcatfrom 6.0.0 · before 6.0.536.0.53
Mavenorg.apache.tomcat:tomcatfrom 7.0.0 · before 7.0.777.0.77
Mavenorg.apache.tomcat:tomcatfrom 8.0.0 · before 8.0.438.0.43
Mavenorg.apache.tomcat:tomcatfrom 8.5.0 · before 8.5.138.5.13
Mavenorg.apache.tomcat:tomcatfrom 9.0.0.M1 · before 9.0.0.M199.0.0.M19
openSUSE:Tumbleweedtomcatbefore 9.0.36-8.49.0.36-8.4
openSUSE:Tumbleweedtomcat10before 10.1.14-1.110.1.14-1.1
Red Hat:enterprise_linux:6::clienttomcat6before 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-admin-webappsbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-docs-webappbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-el-2.1-apibefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-javadocbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-jsp-2.1-apibefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-libbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-servlet-2.5-apibefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:6::clienttomcat6-webappsbefore 0:6.0.24-111.el6_90:6.0.24-111.el6_9
Red Hat:enterprise_linux:7::clienttomcatbefore 0:7.0.76-3.el7_40:7.0.76-3.el7_4
Red Hat:enterprise_linux:7::clienttomcat-admin-webappsbefore 0:7.0.76-3.el7_40:7.0.76-3.el7_4
Red Hat:enterprise_linux:7::clienttomcat-docs-webappbefore 0:7.0.76-3.el7_40:7.0.76-3.el7_4
Red Hat:enterprise_linux:7::clienttomcat-el-2.2-apibefore 0:7.0.76-3.el7_40:7.0.76-3.el7_4
Red Hat:enterprise_linux:7::clienttomcat-javadocbefore 0:7.0.76-3.el7_40:7.0.76-3.el7_4

+96

Other highest-scoring records for the same primary product.

  • CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV
    99Now
  • CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x beforeKEV
    96Now
  • CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV
    92Now
  • CVE-2017-12615When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g.KEV
    92Now
  • CVE-2026-34486Apache Tomcat: Fix for CVE-2026-29146 allowed bypass of EncryptInterceptorKEV
    62This week
  • CVE-2019-0232When running on Windows with enableCmdLineArguments enabled, the CGI Servlet in Apache Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39 and 7.0.0
    62This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:tomcat77.0.28-4+deb7u12 · Debian:7Package registry (OSV)
debian:tomcat88.0.14-1+deb8u9 · Debian:8Package registry (OSV)
Maven:org.apache.tomcat:tomcat6.0.53Package registry (OSV)
Maven:org.apache.tomcat:tomcat7.0.77Package registry (OSV)
Maven:org.apache.tomcat:tomcat8.0.43Package registry (OSV)
Maven:org.apache.tomcat:tomcat8.5.13Package registry (OSV)
Maven:org.apache.tomcat:tomcat9.0.0.M19Package registry (OSV)
opensuse:tomcat9.0.36-8.4 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:tomcat1010.1.14-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:log4j-eap60:1.2.16-12.redhat_3.1.ep6.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat-native0:1.2.8-10.redhat_10.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat-native-debuginfo0:1.2.8-10.redhat_10.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat70:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-admin-webapps0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-docs-webapp0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-el-2.2-api0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-javadoc0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsp-2.2-api0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-jsvc0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-lib0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
red hat:tomcat7-log4j0:7.0.70-22.ep7.el6 · Red Hat:jboss_enterprise_web_server:3.1::el6Package registry (OSV)
suse:tomcat8.0.43-23.1 · SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2Package registry (OSV)
suse:tomcat66.0.53-0.56.1 · SUSE:Linux Enterprise Point of Sale 11 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records