PatchTheCVECVE-2017-12617: Apache Tomcat Remote Code Execution Vulnerability
93
Patch now
HIGH 8.1EXPLOITEDREMOTEWATCHLISTUPGRADEMITIGATEDOWNGRADE
CVE-2017-12617 is a high-severity flaw (CVSS 8.1) affecting tomcat, ubuntu linux, agile product lifecycle management, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
When 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. via setting the readonly initialisation parameter of the Default servlet to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.
Why this priority
- High severity
- EPSS top 1%: very likely to be exploited
- Exploited in the wild (CISA KEV)
- Public exploit reference
- Remotely exploitable, no login, no user action
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.1 (High) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 100.0% (top 1%) |
| CISA exploited list | Yes, fix due 2022-04-15 |
| Weakness | CWE-434 |
| Published | 2017-10-04 |
| Last modified | 2026-08-25 |
Last updated 2026-08-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Exploited Added to the CISA Known Exploited Vulnerabilities list
- Deadline CISA due date for US federal agencies to patch
- Updated Record last modified
apache tomcat UPGRADE
Affected: >= 7.0.0 and < 7.0.82 · >= 8.0 and < 8.0.47 · >= 8.5.0 and < 8.5.23 · >= 9.0.0 and < 9.0.1
Fixed in: 7.0.82, 8.0.47, 8.5.23, 9.0.1
Safe to downgrade to: a release before 7.0.0
1. Check installed version
apt-cache policy tomcat || rpm -q tomcat || tomcat --version
2. UPGRADE to 7.0.82 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade tomcat
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade tomcat
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 7.0.0 (Debian / Ubuntu)
apt-cache madison tomcat
sudo apt install tomcat=<VERSION_BEFORE_7.0.0>
sudo apt-mark hold tomcat
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list tomcat
sudo dnf downgrade tomcat-<VERSION_BEFORE_7.0.0>
sudo dnf versionlock add tomcat
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
canonical ubuntu linux MITIGATE
Affected: 12.04 · 16.04 · 17.10 · 18.04
Fixed in: no fixed release known
Safe to downgrade to: a release before 12.04
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
oracle agile product lifecycle management DOWNGRADE
Affected: 9.3.3 · 9.3.4 · 9.3.5 · 9.3.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.3.3
1. Check installed version
apt-cache policy agile-product-lifecycle-management || rpm -q agile-product-lifecycle-management || agile-product-lifecycle-management --version
2. No fixed release: DOWNGRADE to a release before 9.3.3 (Debian / Ubuntu)
apt-cache madison agile-product-lifecycle-management
sudo apt install agile-product-lifecycle-management=<VERSION_BEFORE_9.3.3>
sudo apt-mark hold agile-product-lifecycle-management
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list agile-product-lifecycle-management
sudo dnf downgrade agile-product-lifecycle-management-<VERSION_BEFORE_9.3.3>
sudo dnf versionlock add agile-product-lifecycle-management
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle communications instant messaging server DOWNGRADE
Affected: 10.0.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 10.0.1
1. Check installed version
apt-cache policy communications-instant-messaging-server || rpm -q communications-instant-messaging-server || communications-instant-messaging-server --version
2. No fixed release: DOWNGRADE to a release before 10.0.1 (Debian / Ubuntu)
apt-cache madison communications-instant-messaging-server
sudo apt install communications-instant-messaging-server=<VERSION_BEFORE_10.0.1>
sudo apt-mark hold communications-instant-messaging-server
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list communications-instant-messaging-server
sudo dnf downgrade communications-instant-messaging-server-<VERSION_BEFORE_10.0.1>
sudo dnf versionlock add communications-instant-messaging-server
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle endeca information discovery integrator DOWNGRADE
Affected: 3.1.0 · 3.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.1.0
1. Check installed version
apt-cache policy endeca-information-discovery-integrator || rpm -q endeca-information-discovery-integrator || endeca-information-discovery-integrator --version
2. No fixed release: DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)
apt-cache madison endeca-information-discovery-integrator
sudo apt install endeca-information-discovery-integrator=<VERSION_BEFORE_3.1.0>
sudo apt-mark hold endeca-information-discovery-integrator
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list endeca-information-discovery-integrator
sudo dnf downgrade endeca-information-discovery-integrator-<VERSION_BEFORE_3.1.0>
sudo dnf versionlock add endeca-information-discovery-integrator
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle enterprise manager for mysql database DOWNGRADE
Affected: 12.1.0.4.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 12.1.0.4.0
1. Check installed version
apt-cache policy enterprise-manager-for-mysql-database || rpm -q enterprise-manager-for-mysql-database || enterprise-manager-for-mysql-database --version
2. No fixed release: DOWNGRADE to a release before 12.1.0.4.0 (Debian / Ubuntu)
apt-cache madison enterprise-manager-for-mysql-database
sudo apt install enterprise-manager-for-mysql-database=<VERSION_BEFORE_12.1.0.4.0>
sudo apt-mark hold enterprise-manager-for-mysql-database
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list enterprise-manager-for-mysql-database
sudo dnf downgrade enterprise-manager-for-mysql-database-<VERSION_BEFORE_12.1.0.4.0>
sudo dnf versionlock add enterprise-manager-for-mysql-database
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Exact fixes by distribution
A distro patch exists: prefer upgrading over downgrading.
Maven · org.apache.tomcat:tomcat-catalina · FIXED · 9.0.1 · vulnerable: >= 9.0.0.M1, <= 9.0.0M27 · source
Set org.apache.tomcat:tomcat-catalina to 9.0.1 or later in pom.xml or build.gradle, then rebuild and redeploy.
Maven · org.apache.tomcat.embed:tomcat-embed-core · FIXED · 9.0.1 · vulnerable: >= 9.0.0.M1, <= 9.0.0M27 · source
Set org.apache.tomcat.embed:tomcat-embed-core to 9.0.1 or later in pom.xml or build.gradle, then rebuild and redeploy.
Fedora 46 · perl-Net-IDN-Encode · FIXED · 2.600-1.fc46 · FEDORA-2026-84eff0ea64 · source
sudo dnf upgrade --advisory=FEDORA-2026-84eff0ea64
Fedora ELN · libXISF · FIXED · 0.2.15-2.eln159 · FEDORA-2026-b9e2d1bda0 · source
sudo dnf upgrade --advisory=FEDORA-2026-b9e2d1bda0
RHEL 6 · tomcat6 · FIXED · tomcat6-6.0.24-111.el6_9
sudo dnf upgrade --advisory=RHSA-2017:3080
rpm -q tomcat6
RHEL 7 · tomcat · FIXED · tomcat-7.0.76-3.el7_4
sudo dnf upgrade --advisory=RHSA-2017:3081
rpm -q tomcat
RHEL 5 · tomcat5 · DEFERRED
sudo yum update --advisory=ALAS-2017-913
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- GitHub PoC: cyberheartmi9/CVE-2017-12617 (400 stars)
- GitHub PoC: LongWayHomie/CVE-2017-12617 (6 stars)
- GitHub PoC: ygouzerh/CVE-2017-12617 (2 stars)
- Write-up: www.exploit-db.com/exploits/42966/
- Exploit-DB: Tomcat - Remote Code Execution via JSP Upload Bypass (Metasploit)
- Exploit-DB: Apache Tomcat < 9.0.1 (Beta) / < 8.5.23 / < 8.0.47 / < 7.0.8 - JSP Upload Bypass / Remote Code Execution (2)
- Metasploit: Tomcat RCE via JSP Upload Bypass
- Nuclei scan template: Apache Tomcat - Remote Code Execution
Verify at the official source NVD · CVE Program · CISA KEV catalog · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-12617?
tomcat: upgrade to 7.0.82, 8.0.47, 8.5.23, 9.0.1; ubuntu linux: mitigate or apply the listed mitigation; agile product lifecycle management: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2017-12617 being exploited?
Yes. CVE-2017-12617 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.
What does CVE-2017-12617 affect?
CVE-2017-12617 affects tomcat, ubuntu linux, agile product lifecycle management. Severity is high (CVSS 8.1). When 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. via setting the readonly initialisation parameter of the Default servlet to false) it was possible
How urgent is CVE-2017-12617?
Priority 93/100. High severity; EPSS top 1%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist
Software pages
Apache Tomcat vulnerabilities · MySQL vulnerabilities · Ubuntu vulnerabilities
Related CVEs
- CVE-2026-34486 HIGH 7.5 EXPLOITED DOWNGRADE DOWNGRADE Apache Tomcat Missing Encryption of Sensitive Data Vulnerability
- CVE-2026-29146 HIGH 7.5 UPGRADE Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration. This issue aff
- CVE-2026-25854 MEDIUM 6.1 UPGRADE Occasional URL redirection to untrusted Site ('Open Redirect') vulnerability in Apache Tomcat via the LoadBala
- CVE-2026-29145 CRITICAL 9.1 UPGRADE UPGRADE CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled vulnerabili
- CVE-2026-24880 HIGH 7.5 UPGRADE Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in Apache Tomca