How severe is CVE-2007-6612?

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

Which packages are affected by CVE-2007-6612?

CVE-2007-6612 affects the following packages: mongrel (RubyGems), mongrel (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2007-6612?

Update mongrel to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-6612 is resolved across your whole dependency graph.

How do I detect CVE-2007-6612 in my RubyGems dependencies?

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

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

Yes. There are 2 known exploit references for CVE-2007-6612, including 2 in-the-wild exploitations 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-6612?

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

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

CVE-2007-6612 was published on May 1, 2022 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

CVE-2007-6612 — mongrel

CVE-2007-6612 is a Path Traversal vulnerability in mongrel. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for mongrel — see the affected versions and patch details below.

Mongrel vulnerable to directory traversal via double-encoded sequences

Published

May 1, 2022

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

💎mongrel💎mongrel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Directory traversal vulnerability in DirHandler (lib/mongrel/handlers.rb) in Mongrel 1.0.4 (1.0.3 and prior are not affected) and 1.1.x before 1.1.3 allows remote attackers to read arbitrary files via an HTTP request containing double-encoded sequences (.%252e).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`mongrel`	≥ 1.0.4&&< 1.0.5	1.0.5`bundle update mongrel --conservative`
💎RubyGems	`mongrel`	≥ 1.1.0&&< 1.1.3	1.1.3`bundle update mongrel --conservative`

Affected Products

1 product · 3 configurations

Application

mongrelmongrel

3 versions

1.0.41.1.11.1.2

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.

Directory traversal vulnerability in DirHandler (lib/mongrel/handlers.rb…

rubyforge.orgNVDMar 2011

Report on rubyforge.org

rubyforge.orgNVDMar 2011

Detection & mitigation playbook

Open-source dependency

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

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works