VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

freewvs: vulnerability history, versions and safety

freewvs is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 6 releases, from Jul 2020 to Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded L2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all freewvs vulnerabilities

Vulert verdict on freewvs 0.1.5 i

Updated on 23 Oct 2026

Action needed: 0.1.5 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 67/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.1.5 — affected i
  • Vulnerabilities on record 4 over 4 years · 0 in the last year i
  • Latest disclosure 30 Aug 2024 i
  • Highest CVSS 2.8 i
  • With no published fix 0 i
  • Stars 41 i
  • Last release 8 months ago i
  • Licence 0BSD i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for freewvs, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.1.5 28 Jan 2026 U2 0BSD Yes Details →
0.1.4 10 Mar 2024 U2 0BSD Yes Details →
0.1.3 15 Jul 2022 U2 non-standard Yes Details →
0.1.2 29 Jan 2022 U2 non-standard Yes Details →
0.1.1 06 Jul 2020 U2 non-standard Yes Details →
0.1.0 23 Dec 2019 L2 U2 non-standard Yes Details →

All 6 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for freewvs

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-15101: freewvs - Nested Directory Structure Interruption 2.8 low 0.1.1 30 Aug 2024
CVE-2020-15100: freewvs vulnerable to denial of service through large files 2.8 low 0.1.1 30 Aug 2024
CVE-2020-15100: freewvs - Large File Denial of Service N/A unrated 18bbf2043e53f69e0119d24f8ae4edb274afb9b2 14 Jul 2020
CVE-2020-15101: freewvs - Directory Structure Recursion Limit Vulnerability N/A unrated 83a6b55c0435c69f447488b791555e6078803143 14 Jul 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About freewvs

Is freewvs safe to use?

Vulert records 4 vulnerabilities for freewvs in PyPI: 0 critical, 0 high, 0 medium and 2 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is freewvs's Vulert package health score?

Vulert scores freewvs 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of freewvs affected?

Yes. 0.1.5, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of freewvs should I use?

0.1.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does freewvs have?

4 vulnerabilities are recorded for freewvs in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 2 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new freewvs vulnerabilities disclosed?

0 vulnerabilities were recorded for freewvs in the last 12 months, and the oldest entry in this database dates to 14 Jul 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of freewvs are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor freewvs for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the freewvs version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.