Skip to main content
CVE-2026-59890VulnerabilityPublished Updated

sdist · setuptools: MANIFEST.in exclusion bypass

Affects shubSource GCVE Database

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

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

Data as of 26 Oct 2026, 19:00 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.18.1
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. Weaponised: 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 26 Oct 2026.

What to do

Upgrade shub to 2.18.1.

Affected software

ProductAffectedFixed in
Homebrewshubpkg:brew/shubOther threatsAffected
  • >=2.15.3 <2.18.1
Fixed in
  • 2.18.1

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 2.18.1 that normalizes both the walked file paths and MANIFEST.in patterns to a canonical Unicode form before matching. Users should upgrade to version 2.18.1 or later. Until then, maintainers should be aware that MANIFEST.in exclusions with non-ASCII filenames may not work correctly on macOS and consider normalizing filenames or patterns manually as a temporary workaround.

Description

A Unicode normalization mismatch in setuptools' handling of MANIFEST.in exclusion patterns can cause excluded files with non-ASCII names to be included in source distributions on macOS APFS/HFS+ filesystems. This occurs because the matching is done byte-for-byte without Unicode normalization, leading to exclusion bypass when the on-disk filename is in NFD form but the MANIFEST.in pattern is in NFC form. This can result in unintended disclosure of files intended to be excluded from published source distributions.

References

Community reviews

Loading reviews…