How severe is CVE-2017-7675?

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

Which packages are affected by CVE-2017-7675?

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

How do I fix CVE-2017-7675?

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

How do I detect CVE-2017-7675 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-7675 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

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

CVE-2017-7675 has an EPSS (Exploit Prediction Scoring System) score of 10.1%, placing it in the 96th 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-7675?

CVE-2017-7675 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2017-7675 was published on August 11, 2017 and was last updated on October 24, 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-7675 — tomcat

HIGHFix: apache/tomcat@cf181ed

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

Improper Limitation of a Pathname to a Restricted Directory in Apache Tomcat

Also known asGHSA-68g5-8q7f-m384

Published

Aug 11, 2017

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

10.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕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

The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.0.M21 and 8.5.0 to 8.5.15 bypassed a number of security checks that prevented directory traversal attacks. It was therefore possible to bypass security constraints using a specially crafted URL.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M1&&< 9.0.0.M22	9.0.0.M22`org.apache.tomcat:tomcat:9.0.0.M22`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.0&&< 8.5.16	8.5.16`org.apache.tomcat:tomcat:8.5.16`

Affected Products

1 product · 37 configurations

Application

tomcatapache

17 versions

8.5.08.5.18.5.28.5.38.5.48.5.58.5.68.5.78.5.88.5.98.5.108.5.11

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.M22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7675 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-7675 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works