VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

fsspec: vulnerability history, versions and safety

fsspec is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 58 releases, first recorded in Oct 2026. 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 H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fsspec vulnerabilities

Vulert verdict on fsspec 2026.9.0 i

Updated on 23 Oct 2026

Good news: 2026.9.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 2026.9.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2026.9.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2026.9.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 47,279 packages i
  • Stars 1,379 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 fsspec, 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
2026.9.0 18 Sep 2026 none BSD-3-Clause — Details →
2026.7.0 28 Jul 2026 none BSD-3-Clause — Details →
2026.6.0 16 Jun 2026 none BSD-3-Clause — Details →
2026.4.0 29 Apr 2026 H1 U1 BSD-3-Clause Yes Details →
2026.3.0 27 Mar 2026 H1 U1 BSD-3-Clause Yes Details →
2026.2.0 05 Feb 2026 H1 U1 BSD-3-Clause Yes Details →
2026.1.0 09 Jan 2026 H1 U1 BSD-3-Clause Yes Details →
2025.12.0 03 Dec 2025 H1 U1 BSD-3-Clause Yes Details →
2025.10.0 30 Oct 2025 H1 U1 BSD-3-Clause Yes Details →
2025.9.0 02 Sep 2025 H1 U1 BSD-3-Clause Yes Details →
2025.7.0 15 Jul 2025 H1 U1 non-standard Yes Details →
2025.5.1 24 May 2025 H1 U1 non-standard Yes Details →
2025.5.0 20 May 2025 H1 U1 non-standard Yes Details →
2025.3.2 31 Mar 2025 H1 U1 non-standard Yes Details →
2025.3.1 30 Mar 2025 H1 U1 non-standard Yes Details →
2025.3.0 07 Mar 2025 H1 U1 non-standard Yes Details →
2025.2.0 01 Feb 2025 H1 U1 non-standard Yes Details →
2024.12.0 19 Dec 2024 H1 U1 non-standard Yes Details →
2024.10.0 21 Oct 2024 H1 U1 non-standard Yes Details →
2024.9.0 04 Sep 2024 H1 U1 non-standard Yes Details →
2024.6.1 27 Jun 2024 H1 U1 non-standard Yes Details →
2024.6.0 04 Jun 2024 H1 U1 non-standard Yes Details →
2024.5.0 15 May 2024 H1 U1 non-standard Yes Details →
2024.3.1 18 Mar 2024 H1 U1 non-standard Yes Details →
2024.3.0 15 Mar 2024 H1 U1 non-standard Yes Details →
2024.2.0 05 Feb 2024 H1 U1 non-standard Yes Details →
2023.12.2 11 Dec 2023 H1 U1 non-standard Yes Details →
2023.12.1 05 Dec 2023 H1 U1 non-standard Yes Details →
2023.12.0 03 Dec 2023 H1 U1 non-standard Yes Details →
2023.10.0 21 Oct 2023 H1 U1 non-standard Yes Details →
2023.9.2 22 Sep 2023 H1 U1 non-standard Yes Details →
2023.9.1 15 Sep 2023 H1 U1 non-standard Yes Details →
2023.9.0 02 Sep 2023 H1 U1 non-standard Yes Details →
2023.6.0 09 Jun 2023 H1 U1 non-standard Yes Details →
2023.5.0 07 May 2023 H1 U1 non-standard Yes Details →
2023.4.0 08 Apr 2023 H1 U1 non-standard Yes Details →
2023.3.0 04 Mar 2023 H1 U1 non-standard Yes Details →
2023.1.0 19 Jan 2023 H1 U1 non-standard Yes Details →
2022.11.0 10 Nov 2022 H1 U1 non-standard Yes Details →
2022.10.0 19 Oct 2022 H1 U1 non-standard Yes Details →
2022.8.2 01 Sep 2022 H1 U1 non-standard Yes Details →
2022.8.1 31 Aug 2022 H1 U1 non-standard Yes Details →
2022.8.0 30 Aug 2022 H1 U1 non-standard Yes Details →
2022.7.1 29 Jul 2022 H1 U1 non-standard Yes Details →
2022.7.0 27 Jul 2022 H1 U1 non-standard Yes Details →
2022.5.0 19 May 2022 H1 U1 non-standard Yes Details →
2022.3.0 31 Mar 2022 H1 U1 non-standard Yes Details →
2022.2.0 22 Feb 2022 H1 U1 non-standard Yes Details →
2022.1.0 11 Jan 2022 H1 U1 non-standard Yes Details →
2021.11.1 26 Nov 2021 H1 U1 non-standard Yes Details →
2021.11.0 05 Nov 2021 H1 U1 non-standard Yes Details →
2021.10.1 15 Oct 2021 H1 U1 non-standard Yes Details →
2021.10.0 02 Oct 2021 H1 U1 non-standard Yes Details →
2021.9.0 23 Sep 2021 H1 U1 non-standard Yes Details →
2021.8.1 31 Aug 2021 H1 U1 non-standard Yes Details →
2021.7.0 13 Jul 2021 H1 U1 non-standard Yes Details →
2021.6.1 23 Jun 2021 H1 U1 non-standard Yes Details →
2021.6.0 07 Jun 2021 H1 U1 non-standard Yes Details →
2021.5.0 14 May 2021 H1 U1 non-standard Yes Details →
2021.4.0 16 Apr 2021 H1 U1 non-standard Yes Details →
0.9.0 05 Apr 2021 H1 U1 non-standard Yes Details →
0.8.7 23 Feb 2021 none non-standard — Details →
0.8.6 23 Feb 2021 none non-standard — Details →
0.8.5 15 Dec 2020 none non-standard — Details →
0.8.4 14 Oct 2020 none non-standard — Details →
0.8.3 24 Sep 2020 none non-standard — Details →
0.8.2 10 Sep 2020 none non-standard — Details →
0.8.1 09 Sep 2020 none non-standard — Details →
0.8.0 31 Jul 2020 none non-standard — Details →
0.7.4 19 May 2020 none non-standard — Details →
0.7.3 22 Apr 2020 none non-standard — Details →
0.7.2 07 Apr 2020 none non-standard — Details →
0.7.1 30 Mar 2020 none non-standard — Details →
0.7.0 27 Mar 2020 none non-standard — Details →
0.6.3 20 Mar 2020 none non-standard — Details →
0.6.2 16 Dec 2019 none non-standard — Details →
0.6.1 27 Nov 2019 none non-standard — Details →
0.6.0 13 Nov 2019 none non-standard — Details →
0.5.2 06 Oct 2019 none non-standard — Details →
0.5.1 19 Sep 2019 none non-standard — Details →
0.4.5 16 Sep 2019 none non-standard — Details →
0.4.4 03 Sep 2019 none non-standard — Details →
0.4.3 27 Aug 2019 none non-standard — Details →
0.4.2 27 Aug 2019 none non-standard — Details →
0.4.1 05 Aug 2019 none non-standard — Details →
0.4.0 31 Jul 2019 none non-standard — Details →
0.3.6 25 Jul 2019 none non-standard — Details →
0.3.5 24 Jul 2019 none non-standard — Details →
0.3.4 22 Jul 2019 none non-standard — Details →
0.3.3 18 Jul 2019 none non-standard — Details →
0.3.2 17 Jul 2019 none non-standard — Details →
0.3.1 17 Jul 2019 none non-standard — Details →
0.3.0 09 Jul 2019 none non-standard — Details →
0.2.3 01 Jul 2019 none non-standard — Details →
0.2.2 30 Jun 2019 none non-standard — Details →
0.2.1 18 Jun 2019 none non-standard — Details →
0.2.0 22 Feb 2019 none non-standard — Details →
0.1.4 05 Feb 2019 none non-standard — Details →
0.1.3 10 Jan 2019 none non-standard — Details →
0.1.2 09 Jan 2019 none non-standard — Details →
0.1.1 02 Jan 2019 none — — Details →
0.1.0 02 Jan 2019 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for fsspec

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-104851: fsspec Remote Code Execution via Server-Side Template Injection 8.8 high 2026.6.0 05 Oct 2026
CVE-2026-104851: fsspec Remote Code Execution via Server-Side Template Injection 8.8 high 2026.6.0 15 Oct 2026

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 fsspec

Is fsspec safe to use?

Vulert records 2 vulnerabilities for fsspec in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 fsspec's Vulert package health score?

Vulert scores fsspec 80/100, which reads as in good shape. 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 fsspec affected?

No. 2026.9.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of fsspec should I use?

2026.9.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 fsspec have?

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

2 vulnerabilities were recorded for fsspec in the last 12 months, and the oldest entry in this database dates to 05 Oct 2026. 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 fsspec 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 fsspec for upcoming vulnerabilities?

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