How severe is CVE-2010-3718?

No CVSS score has been assigned to CVE-2010-3718 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-3718?

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

How do I fix CVE-2010-3718?

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

How do I detect CVE-2010-3718 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-2010-3718 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-2010-3718 actively exploited in the wild?

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

CVE-2010-3718 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2010-3718 published, and has it been updated?

CVE-2010-3718 was published on May 14, 2022 and was last updated on February 21, 2024. 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

CVE-2010-3718 — tomcat

Fix: apache/tomcat@a697f7b

CVE-2010-3718 is a security vulnerability in org.apache.tomcat:tomcat. 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

Published

May 14, 2022

Updated

Feb 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

☕org.apache.tomcat:tomcat☕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

Apache Tomcat 7.0.0 through 7.0.3, 6.0.x, and 5.5.x, when running within a SecurityManager, does not make the ServletContext attribute read-only, which allows local web applications to read or write files outside of the intended working directory, as demonstrated using a directory traversal attack.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.4	7.0.4`org.apache.tomcat:tomcat:7.0.4`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.30	6.0.30`org.apache.tomcat:tomcat:6.0.30`
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.30	5.5.30`org.apache.tomcat:tomcat:5.5.30`

Affected Products

1 product · 63 configurations

Application

tomcatapache

63 versions

5.5.05.5.15.5.25.5.35.5.45.5.55.5.65.5.75.5.85.5.95.5.105.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 7.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3718 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.

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 HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.22.el5_7`	RHSA-2011:1845
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-33.el6`	RHSA-2011:0791
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`ant-0:1.7.1-13.jdk6.ep5.el5`	RHSA-2011:0897
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2011:0896

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-3718 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works