How severe is CVE-2017-12615?

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

Which packages are affected by CVE-2017-12615?

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

How do I fix CVE-2017-12615?

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

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

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

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

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

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

Yes. There are 24 known exploit references for CVE-2017-12615, including 1 documented proof-of-concept exploit on Exploit-DB and 14 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2017-12615 has an EPSS (Exploit Prediction Scoring System) score of 99.6%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-12615 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-12615 (Apache Tomcat on Windows Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-15. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-12615?

CVE-2017-12615 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2017-12615?

A Nuclei detection template exists for CVE-2017-12615, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2017-12615 was published on September 19, 2017 and was last updated on October 20, 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

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2017-12615 — tomcat-embed-core

HIGH

CVE-2017-12615 is a high-severity (CVSS 8.1) Unrestricted File Upload vulnerability in org.apache.tomcat.embed:tomcat-embed-core. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-25) and has been used in ransomware campaigns — treat it as actively exploited and patch now. A fix is available for org.apache.tomcat.embed:tomcat-embed-core — see the affected versions and patch details below.

When running Apache Tomcat on Windows with HTTP PUTs enabled it was possible to upload a JSP file to the server

Also known asGHSA-pjfr-qf3p-3q25

Published

Sep 19, 2017

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

24 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-25 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-04-15.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-12615.

EPSS Exploitation Probability

via FIRST.org ↗

99.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2017-12615 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕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

When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 7.0.0&&< 7.0.79	7.0.79`org.apache.tomcat.embed:tomcat-embed-core:7.0.79`

Affected Products

22 products · 50 configurations

Application

tomcatapache

≥ 7.0.0 && ≤ 7.0.79

range

Application

7-mode transition toolnetapp

all

Application

oncommand balancenetapp

all

Application

oncommand shiftnetapp

all

enterprise linux desktopredhat

2 versions

6.07.0

enterprise linux eusredhat

4 versions

7.47.57.67.7

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-42953webappswindows

Apache Tomcat < 9.0.1 (Beta) / < 8.5.23 / < 8.0.47 / < 7.0.8 - JSP Upload Bypass / Remote Code Execution (1)

by xxlegend · Sep 20, 2017

Exploit-DB Source

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.embed:tomcat-embed-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat.embed:tomcat-embed-core to 7.0.79 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-12615 is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

How to detect CVE-2017-12615

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2017-12615 -u https://target

Template: Apache Tomcat Servers - Remote Code Execution
Severity: high
Impact: Successful exploitation of this vulnerability allows an attacker to execute arbitrary code on the affected server.
Remediation: Apply the latest security patches or upgrade to a non-vulnerable version of Apache Tomcat.

Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

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

This flaw affects Tomcat on Red Hat Enterprise Linux only when a specific context is configured with readonly=false. The default configuration has a readonly context, so it is not affected.

Workaround published by Red Hat

Ensure that readonly is set to true (the default) for the DefaultServlet, WebDAV servlet or application context. Block HTTP methods that permit resource modification for untrusted users.

Source: Red Hat security advisory for CVE-2017-12615 (CC BY 4.0)

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	`httpd-0:2.2.26-57.ep6.el6`	RHSA-2017:3113
Red Hat JBoss Web Server 2.1	`tomcat6`	RHSA-2017:3114
Red Hat JBoss Web Server 3.1	see advisory	RHSA-2018:0465
Red Hat JBoss Web Server 3 for RHEL 6	`mod_cluster-0:1.3.8-2.Final_redhat_2.1.ep7.el6`	RHSA-2018:0466

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-12615 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2017-12615 — tomcat-embed-core

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2017-12615

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2017-12615 in your dependencies?