Exploited CVEs / Apache / CVE-2017-12617
CVE-2017-12617
Apache Tomcat Remote Code Execution Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-04-15 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Actively exploited Apache Tomcat vulnerability, High severity, CVSS 8.1. Added to the CISA KEV catalog 2022-03-25.
Risk summary
Updated July 28, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2017-12617
An EPSS score of 100% tells the story: uploading a JSP file to Apache Tomcat through a specially crafted request, then requesting it to run the code, is fully automated by attackers and still works against unpatched servers. Severity is High (CVSS 8.1) and exploitation is confirmed (KEV 2022-03-25). Tomcat is embedded in a huge range of enterprise products, so exposure extends well past standalone installs.
Do this: Inventory Tomcat instances, including those bundled inside vendor products, and patch or disable HTTP PUT where enabled.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2017-12617
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2017-12617
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2022-04-15 (past due).
Apply updates per vendor instructions.
Official fix for CVE-2017-12617
Check the vendor's security advisory channel for the patched Tomcat versions and workarounds.
Common questions about CVE-2017-12617
Is CVE-2017-12617 actively exploited?
Yes. CVE-2017-12617 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%.
What is the CISA deadline and required action for CVE-2017-12617?
CISA set the federal (BOD 22-01) remediation due date at 2022-04-15, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions.
What fixes CVE-2017-12617?
Check the vendor's security advisory for the patched Tomcat versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2017-12617?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2017-12617's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
More exploited Apache CVEs
The newest Apache entries on the CISA KEV catalog:
All Apache exploited CVEs on one page: Apache vulnerabilities actively exploited.
Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.
