freewvs's nested directory structure can interrupt scan

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.4 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2020-15101: 0.69% estimated exploitation activity in the next 30 days; percentile 52.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A directory structure of more than 1000 nested directories can interrupt a freewvs scan due to Python's recursion limit and os.walk(). This can be problematic in a case where an administrator scans the dirs of potentially untrusted users. Patches This has been fixed in this commit by limiting the recursion to 500 directories: https://github.com/schokokeksorg/freewvs/commit/83a6b55c0435c69f447488b791555e6078803143 This issue was discovered by Hanno Böck.

Published by the source

30 Aug 2024, 18:43 UTC

Last modified by the source

8 Jul 2026, 06:00 UTC

Source last checked

26 Oct 2026, 13:16 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7pmh-vrww-25xx

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7pmh-vrww-25xx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15101

Advisory: freewvs's nested directory structure can interrupt scan
IDs: CVE-2020-15101, GHSA-7pmh-vrww-25xx
Record: https://patchnext.com/advisories/cve-2020-15101 (revision 3, source checked 26 Oct 2026, 13:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: freewvs 0.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI freewvs: affected < 0.1.1; fixed in 0.1.1

## Suggested inspection (read-only)
- `python -m pip show freewvs`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on freewvs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7pmh-vrww-25xx (OSV record GHSA-7pmh-vrww-25xx lists affected ranges: PyPI freewvs >=0 <0.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-7pmh-vrww-25xx (GitHub-reviewed advisory GHSA-7pmh-vrww-25xx lists affected ranges: PyPI freewvs >=0 <0.1.1)

Commands are suggestions: review each one before running it.