Skip to main content
VulnerabilityPublished Updated

CVE-2026-24486: Datasette · Python-Multipart has Arbitrary File Write via Non-Default Configuration

Affects datasetteSource GCVE Database

0
Compare
Authoritative record:CVE-2026-24486· High 8.6

Public exploit available (Exploit-DB) · CVSS 8.6 High : upgrade to 0.65.2_1 as a priority.

Data as of 18 Nov 2026, 18:34 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.65.2_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 4 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 17 minutes after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    Python-Multipart 0.0.22 - Path Traversal

    , 93 days after disclosure

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_1.

Affected software

ProductAffectedFixed in
Homebrewdatasettepkg:brew/datasetteOther threatsAffected
  • >=0.47.3 <0.65.2_1
Fixed in
  • 0.65.2_1

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

AI-suggested

Upgrade Datasette to version 0.65.2_1 or later where this vulnerability is fixed. Alternatively, avoid using the configuration option UPLOAD_KEEP_FILENAME=True. The default configuration is not vulnerable.

Description

Datasette's Python-Multipart library has a path traversal vulnerability when configured with UPLOAD_DIR set and UPLOAD_KEEP_FILENAME=True. This allows an attacker to write uploaded files to arbitrary filesystem locations by using filenames starting with a slash. The vulnerability only affects configurations where uploaded files exceed MAX_MEMORY_FILE_SIZE, triggering a disk flush. The default configuration is not vulnerable. A fix is available in version 0.65.2_1.

References

Community reviews

Loading reviews…