Skip to main content
VulnerabilityPublished Updated

CVE-2026-64847: Datasette · AnyIO process-pool workers can block indefinitely on undrained stderr

Affects datasetteSource GCVE Database

0
Compare
Authoritative record:CVE-2026-64847· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium : upgrade to 0.65.2_6 when convenient.

Data as of 18 Nov 2026, 18:49 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.65.2_6
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade datasette to 0.65.2_6.

Affected software

ProductAffectedFixed in
Homebrewdatasettepkg:brew/datasetteOther threatsAffected
  • >=0.58 <0.65.2_6
Fixed in
  • 0.65.2_6

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

AI-suggested

A patch is available in Datasette version 0.65.2_6 and should be applied to resolve the issue. As a workaround, closing sys.stderr in the target function can prevent the deadlock. Users should update to the fixed version to fully mitigate the vulnerability.

Description

Datasette versions from 0.58 up to but not including 0.65.2_6 contain a vulnerability where AnyIO process-pool workers can block indefinitely due to undrained stderr pipes. The worker redirects stdin and stdout to /dev/null but does not redirect stderr, allowing attacker-influenced stderr output to fill the pipe and cause a deadlock. This affects users running untrusted or faulty code that writes excessive data to stderr. A fix is available in version 0.65.2_6. Closing sys.stderr in the target function can mitigate the issue temporarily.

References

Community reviews

Loading reviews…