VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nfstream: vulnerability history, versions and safety

nfstream is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 81 releases, from Feb 2021 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 nfstream vulnerabilities

Vulert verdict on nfstream 6.6.0 i

Updated on 23 Oct 2026

Careful: 6.6.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.6.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 5.5 i
  • With no published fix 1 i
  • Depended on by 2 packages i
  • Stars 1,224 i
  • OpenSSF scorecard 5/10 i
  • Last release 8 months ago i
  • Licence LGPL-3.0-or-later 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 nfstream, 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
6.6.0 16 Feb 2026 M1 LGPL-3.0-or-later No Details →
6.5.4 18 Nov 2025 M1 LGPL-3.0-or-later No Details →
6.5.3 26 Oct 2022 M1 LGPL-3.0 No Details →
6.5.2 27 Sep 2022 M1 LGPL-3.0 No Details →
6.5.1 27 Apr 2022 M1 LGPL-3.0 No Details →
6.4.3 16 Mar 2022 M1 LGPL-3.0 No Details →
6.4.2 11 Feb 2022 M1 LGPL-3.0 No Details →
6.4.1 10 Feb 2022 M1 LGPL-3.0 No Details →
6.4.0 10 Dec 2021 M1 LGPL-3.0 No Details →
6.3.5 07 Oct 2021 M1 LGPL-3.0 No Details →
6.3.4 03 Sep 2021 M1 LGPL-3.0 No Details →
6.3.3 02 Jul 2021 M1 LGPL-3.0 No Details →
6.3.2 10 Jun 2021 M1 LGPL-3.0 No Details →
6.3.1 22 Apr 2021 M1 LGPL-3.0 No Details →
6.3.0 21 Apr 2021 M1 LGPL-3.0 No Details →
6.2.6 14 Apr 2021 M1 LGPL-3.0 No Details →
6.2.5 27 Nov 2020 M1 LGPL-3.0 No Details →
6.2.4 23 Nov 2020 M1 LGPL-3.0 No Details →
6.2.3 15 Nov 2020 M1 LGPL-3.0 No Details →
6.2.2 10 Nov 2020 M1 LGPL-3.0 No Details →
6.2.1 10 Nov 2020 M1 LGPL-3.0 No Details →
6.2.0 21 Oct 2020 M1 LGPL-3.0 No Details →
6.1.3 21 Sep 2020 M1 LGPL-3.0 No Details →
6.1.2 17 Sep 2020 M1 LGPL-3.0 No Details →
6.1.1 14 Sep 2020 M1 LGPL-3.0 No Details →
6.1.0 14 Sep 2020 M1 LGPL-3.0 No Details →
6.0.5 13 Sep 2020 M1 LGPL-3.0 No Details →
6.0.4 12 Sep 2020 M1 LGPL-3.0 No Details →
6.0.3 10 Sep 2020 M1 LGPL-3.0 No Details →
6.0.2 08 Sep 2020 M1 LGPL-3.0 No Details →
6.0.0 08 Sep 2020 M1 LGPL-3.0 No Details →
5.2.0 18 Jul 2020 M1 U1 LGPL-3.0 No Details →
5.1.6 11 Jul 2020 U1 LGPL-3.0 Yes Details →
5.1.5 23 May 2020 U1 LGPL-3.0 Yes Details →
5.1.3 21 May 2020 U1 LGPL-3.0 Yes Details →
5.1.2 19 May 2020 U1 LGPL-3.0 Yes Details →
5.1.1 18 May 2020 U1 LGPL-3.0 Yes Details →
5.1.0 07 May 2020 U1 LGPL-3.0 Yes Details →
5.0.0 06 May 2020 U1 LGPL-3.0 Yes Details →
4.0.1 23 Apr 2020 U1 LGPL-3.0 Yes Details →
4.0.0 15 Apr 2020 U1 LGPL-3.0 Yes Details →
3.2.2 29 Feb 2020 U1 LGPL-3.0 Yes Details →
3.2.1 29 Feb 2020 U1 LGPL-3.0 Yes Details →
3.2.0 20 Feb 2020 U1 LGPL-3.0 Yes Details →
3.1.2 07 Jan 2020 U1 LGPL-3.0 Yes Details →
3.1.1 29 Dec 2019 U1 LGPL-3.0 Yes Details →
3.1.0 29 Dec 2019 U1 LGPL-3.0 Yes Details →
3.0.4 18 Dec 2019 U1 LGPL-3.0 Yes Details →
3.0.3 18 Dec 2019 U1 LGPL-3.0 Yes Details →
3.0.2 06 Dec 2019 U1 LGPL-3.0 Yes Details →
3.0.1 04 Dec 2019 U1 LGPL-3.0 Yes Details →
3.0.0 04 Dec 2019 U1 LGPL-3.0 Yes Details →
2.0.1 29 Nov 2019 U1 LGPL-3.0 Yes Details →
2.0.0 28 Nov 2019 U1 LGPL-3.0 Yes Details →
1.2.1 15 Nov 2019 U1 LGPL-3.0 Yes Details →
1.2.0 14 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.8 07 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.7 07 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.6 04 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.5 02 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.4 02 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.3 02 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.2 02 Nov 2019 U1 LGPL-3.0 Yes Details →
1.1.1 02 Nov 2019 U1 LGPL-3.0 Yes Details →
1.0.3 31 Oct 2019 U1 LGPL-3.0 Yes Details →
1.0.2 31 Oct 2019 U1 LGPL-3.0 Yes Details →
1.0.1 31 Oct 2019 U1 LGPL-3.0 Yes Details →
1.0.0 30 Oct 2019 U1 LGPL-3.0 Yes Details →
0.5.0 21 Oct 2019 U1 LGPL-3.0 Yes Details →
0.4.0 20 Oct 2019 U1 LGPL-3.0 Yes Details →
0.3.1 20 Oct 2019 U1 LGPL-3.0 Yes Details →
0.3.0 20 Oct 2019 U1 LGPL-3.0 Yes Details →
0.2.0 19 Oct 2019 U1 LGPL-3.0 Yes Details →
0.1.0 19 Oct 2019 U1 LGPL-3.0 Yes Details →
1.0.0-py3.6 — M1 U1 — No Details →
1.0.1-py3.6 — M1 U1 — No Details →
1.0.2-py3.6 — M1 U1 — No Details →
1.0.3-py3.6 — M1 U1 — No Details →
1.1.0 — U1 — Yes Details →
5.1.4 — U1 — Yes Details →
6.5.0 — M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for nfstream

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-25340: NFStream Local Denial of Service (DoS) 5.5 medium No fix published 24 May 2022
CVE-2020-25340: Memory Leak Vulnerability in nfstream N/A unrated 6.0.0 16 Feb 2021

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 nfstream

Is nfstream safe to use?

Vulert records 2 vulnerabilities for nfstream in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is nfstream's Vulert package health score?

Vulert scores nfstream 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of nfstream affected?

Yes. 6.6.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of nfstream should I use?

6.6.0 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 nfstream have?

2 vulnerabilities are recorded for nfstream in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 nfstream vulnerabilities disclosed?

0 vulnerabilities were recorded for nfstream in the last 12 months, and the oldest entry in this database dates to 16 Feb 2021. 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 nfstream 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 nfstream for upcoming vulnerabilities?

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