Skip to main content
VulnerabilityPublished Updated

CVE-2026-104851: fsspec filesystem_spec · Code Injection

Affects fsspec filesystem_specSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2026.6.0 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.6.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade filesystem_spec and fsspec to 2026.6.0.

Affected software

ProductAffectedFixed in
fsspecfilesystem_specAffected
  • >=0.9.0 <2026.6.0
Fixed in
  • 2026.6.0
PyPIfsspecpkg:pypi/fsspecOther threatsAffected
  • >=0.9.0 <2026.6.0
Fixed in
  • 2026.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to fsspec version 2026.6.0 or later, where this vulnerability is fixed. No other mitigations are specified. Patch status is confirmed fixed in 2026.6.0.

Description

CVE-2026-104851 is a high-severity code injection vulnerability in the fsspec filesystem_spec Python library. Versions from 0.9.0 up to but not including 2026.6.0 allow attacker-controlled Kerchunk reference JSON documents to execute arbitrary Python code via unsafe jinja2 template rendering when opening the reference filesystem. This can occur before any referenced data is read and affects multiple code paths depending on document content and options. The issue is fixed in version 2026.6.0.

References

Community reviews

Loading reviews…