How severe is CVE-2007-6672?

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

Which packages are affected by CVE-2007-6672?

CVE-2007-6672 affects the following packages: org.mortbay.jetty:jetty (Maven). Ecosystems affected: Maven.

How do I fix CVE-2007-6672?

Update org.mortbay.jetty:jetty to 6.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-6672 is resolved across your whole dependency graph.

How do I detect CVE-2007-6672 in my Maven dependencies?

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

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

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

CVE-2007-6672 has an EPSS (Exploit Prediction Scoring System) score of 3.9%, placing it in the 90th 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.

What type of vulnerability is CVE-2007-6672?

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

CVE-2007-6672 was published on May 1, 2022 and was last updated on December 6, 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-6672 — jetty

CVE-2007-6672 is a Path Traversal vulnerability in org.mortbay.jetty:jetty. A fix is available for org.mortbay.jetty:jetty — see the affected versions and patch details below.

Mortbay Jetty Double Slash URI Information Disclosure Vulnerability

Published

May 1, 2022

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.mortbay.jetty:jetty

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

Mortbay Jetty 6.1.5 and 6.1.6 allows remote attackers to bypass protection mechanisms and read the source of files via multiple / (slash) characters in the URI.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mortbay.jetty:jetty`	≥ 6.1.5&&< 6.1.7	6.1.7`org.mortbay.jetty:jetty:6.1.7`

Affected Products

1 product · 2 configurations

Application

jettymortbay_jetty

2 versions

6.1.56.1.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mortbay.jetty:jetty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.mortbay.jetty:jetty to 6.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-6672 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

Mortbay Jetty 6.1.5 and 6.1.6 allows remote attackers to bypass protection mechanisms and read the source of files via multiple `/` (slash) characters in the URI.

O3 Security · Impact-Aware SCA

Is CVE-2007-6672 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works