Skip to main content
CVE-2026-59890VulnerabilityPublished Updated

sdist · setuptools: MANIFEST.in exclusion bypass

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-59890· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.0.2 when convenient.

Data as of 22 Nov 2026, 18:23 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 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 21 Nov 2026.

What to do

Upgrade standardebooks to 4.0.2.

Affected software

ProductAffectedFixed in
Homebrewstandardebookspkg:brew/standardebooksOther threatsAffected
  • >=2.9.2 <4.0.2
Fixed in
  • 4.0.2

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

AI-suggested

A fix is available in setuptools version 4.0.2 that normalizes both the on-disk filenames and MANIFEST.in patterns to a canonical Unicode form before matching, preventing exclusion bypass. Users should upgrade to version 4.0.2 or later. Until upgraded, maintainers should be aware that MANIFEST.in exclusions may not work as expected for non-ASCII filenames on macOS filesystems and consider additional manual checks or renaming files to ASCII-only names.

Description

A Unicode normalization mismatch in setuptools' MANIFEST.in exclusion handling can cause excluded files with non-ASCII names to be included in source distributions on macOS APFS/HFS+ filesystems. This occurs because the filesystem uses NFD normalization for filenames, while MANIFEST.in patterns are typically written in NFC, leading to a byte-level mismatch and bypass of exclusion rules. This can result in unintended disclosure of files intended to be excluded from published packages.

References

Community reviews

Loading reviews…