Skip to main content
CVE-2026-59890VulnerabilityPublished Updated

sdist · setuptools: MANIFEST.in exclusion bypass

Affects ccmSource GCVE Database

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

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

Data as of 26 Oct 2026, 19:43 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.1.5_6
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 ccm to 3.1.5_6.

Affected software

ProductAffectedFixed in
Homebrewccmpkg:brew/ccmOther threatsAffected
  • >=3.1.5_3 <3.1.5_6
Fixed in
  • 3.1.5_6

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 3.1.5_6. Users should upgrade to this version or later to ensure that both MANIFEST.in patterns and on-disk filenames are normalized to a canonical Unicode form before matching, preventing exclusion bypass. Until upgrading, maintainers should be aware that MANIFEST.in exclusions may not work correctly for non-ASCII filenames on macOS APFS/HFS+ filesystems.

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 because on macOS APFS/HFS+ filesystems, filenames are stored in NFD form, but MANIFEST.in patterns are typically written in NFC form, leading to a byte-level mismatch during exclusion matching. As a result, sensitive files with non-ASCII names may be unintentionally published to PyPI. The issue affects setuptools versions prior to 3.1.5_6 and has been fixed in 3.1.5_6.

References

Community reviews

Loading reviews…