Skip to main content
CVE-2026-59890VulnerabilityPublished Updated

sdist · setuptools: MANIFEST.in exclusion bypass

Affects mycliSource GCVE Database

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

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

Data as of 30 Oct 2026, 08:46 UTC

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

What to do

Upgrade mycli to 2.7.0.

Affected software

ProductAffectedFixed in
Homebrewmyclipkg:brew/mycliOther threatsAffected
  • >=1.38.0 <2.7.0
Fixed in
  • 2.7.0

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 setuptools version 2.7.0 that normalizes both the walked file paths and MANIFEST.in patterns to a canonical Unicode form before matching, preventing exclusion bypass. Users should upgrade to setuptools 2.7.0 or later. Until upgraded, maintainers should be aware that MANIFEST.in exclusions are normalization-insensitive on macOS and consider erring on the side of excluding more files. No other immediate actions are required.

Description

A Unicode normalization mismatch in setuptools' handling of MANIFEST.in exclusions can cause files intended to be excluded from source distributions to be included instead. This occurs on macOS APFS/HFS+ filesystems where filenames are stored in NFD form but MANIFEST.in patterns are typically written in NFC form, causing byte-level matching to fail. As a result, non-ASCII files meant to be excluded may be published publicly on PyPI, potentially exposing secrets or private files. ASCII-only exclusions are unaffected. A fix is available in setuptools 2.7.0.

References

Community reviews

Loading reviews…