How severe is CVE-2007-5461?

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

Which packages are affected by CVE-2007-5461?

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

How do I fix CVE-2007-5461?

The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2007-5461. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

Yes. There are 3 known exploit references for CVE-2007-5461, including 2 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation 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-2007-5461?

CVE-2007-5461 has an EPSS (Exploit Prediction Scoring System) score of 39.7%, placing it in the 99th 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-2007-5461?

CVE-2007-5461 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-2007-5461 published, and has it been updated?

CVE-2007-5461 was published on May 1, 2022 and was last updated on January 8, 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-2007-5461 — tomcat

Fix: apache/tomcat@1e7b31e

CVE-2007-5461 is a Path Traversal vulnerability in org.apache.tomcat:tomcat. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Apache Tomcat Path Traversal Vulnerability

Published

May 1, 2022

Updated

Jan 8, 2024

Affected

5 pkgs

Patched

See advisory

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

39.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

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

Real-World Exposure

5 pkgs affected

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

Absolute path traversal vulnerability in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0, 5.0.0, 5.5.0 through 5.5.25, and 6.0.0 through 6.0.14, under certain configurations, allows remote authenticated users to read arbitrary files via a WebDAV write request that specifies an entity with a SYSTEM tag.

Affected Packages

5 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.0.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	all versions	No fix
☕Maven	`org.apache.tomcat:tomcat`	all versions	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0	No fix

Affected Products

1 product · 44 configurations

Application

tomcatapache

44 versions

4.0.04.0.14.0.24.0.34.0.44.0.54.0.64.1.04.1.14.1.24.1.34.1.4

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-4552remotelinux✓ Verified

Apache Tomcat - WebDAV SSL Remote File Disclosure

by h3rcul3s · Oct 21, 2007

Exploit-DB Source

EDB-4530remotemultiple✓ Verified

Apache Tomcat - 'WebDAV' Remote File Disclosure

by eliteboy · Oct 14, 2007

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:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2007-5461. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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 HatImportant

Product	Fixed in	Advisory
JBEAP 4.2.0 for RHEL 4	`glassfish-javamail-0:1.4.0-0jpp.ep1.8`	RHSA-2008:0151
JBEAP 4.2.0 for RHEL 5	`hibernate3-0:3.2.4-1.SP1_CP02.0jpp.ep1.1.el5.1`	RHSA-2008:0213
Red Hat Certificate System 7.3	`ant-0:1.6.5-1jpp_1rh`	RHSA-2010:0602
Red Hat Developer Suite V.3	`tomcat5-0:5.5.23-0jpp_11rh`	RHSA-2008:0195
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.3.0.3.el5_1`	RHSA-2008:0042
Red Hat Network Satellite Server v 4.2	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0524
Red Hat Network Satellite Server v 5.0	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0261
Red Hat Network Satellite Server v 5.1	`jfreechart-0:0.9.20-3.rhn`	RHSA-2008:0630

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2007-5461 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works