CVE-2021-29061 is a high-severity (CVSS 7.5) CWE-770 vulnerability in com.github.fracpete:vfsjfilechooser2. 3 public exploit references exist, so weaponization risk is real. A fix is available for com.github.fracpete:vfsjfilechooser2 — see the affected versions and patch details below.
ReDOS in Vfsjfilechooser2
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-29061 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.github.fracpete:vfsjfilechooser2Real-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
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Vfsjfilechooser2 version 0.2.9 and below which occurs when the application attempts to validate crafted URIs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.github.fracpete:vfsjfilechooser2 | all versions | 0.2.9com.github.fracpete:vfsjfilechooser2:0.2.9 |
Affected Products
vfsjfilechooser2vfsjfilechooser2_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.github.fracpete:vfsjfilechooser2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.github.fracpete:vfsjfilechooser2 to 0.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-29061 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2021-29061 in your dependencies?
Find it across Maven, including transitive dependencies.