How severe is CVE-2006-2758?

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

Which packages are affected by CVE-2006-2758?

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

How do I fix CVE-2006-2758?

The records we use list no patched version of org.mortbay.jetty:jetty for CVE-2006-2758. 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-2006-2758 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-2006-2758 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-2006-2758 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2006-2758, including 1 documented proof-of-concept exploit 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-2006-2758?

CVE-2006-2758 has an EPSS (Exploit Prediction Scoring System) score of 4.0%, placing it in the 91th 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-2006-2758?

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

CVE-2006-2758 was published on May 1, 2022 and was last updated on November 28, 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-2006-2758 — jetty

CVE-2006-2758 is a Path Traversal vulnerability in org.mortbay.jetty:jetty. 2 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.

Jetty Directory Traversal Vulnerability

Published

May 1, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

See advisory

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

4.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% 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

Directory traversal vulnerability in jetty 6.0.x (jetty6) beta16 allows remote attackers to read arbitrary files via a %2e%2e%5c (encoded ../) in the URL. NOTE: this might be the same issue as CVE-2005-3747.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mortbay.jetty:jetty`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

jettyjetty

1 version

6.0

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-18571webappsphp

promise webpam 2.2.0.13 - Multiple Vulnerabilities

by LiquidWorm · Mar 7, 2012

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.mortbay.jetty:jetty, 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.mortbay.jetty:jetty for CVE-2006-2758. 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.

Frequently Asked Questions

Directory traversal vulnerability in jetty 6.0.x (jetty6) beta16 allows remote attackers to read arbitrary files via a `%2e%2e%5c` (encoded `../`) in the URL. NOTE: this might be the same issue as CVE-2005-3747.

O3 Security · Impact-Aware SCA

Is CVE-2006-2758 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works