Skip to main content
CVE-2026-59890VulnerabilityPublished Updated

sdist · setuptools: MANIFEST.in exclusion bypass

Affects redexSource GCVE Database

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

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

Data as of 26 Oct 2026, 19:42 UTC

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

Affected software

ProductAffectedFixed in
Homebrewredexpkg:brew/redexOther threatsAffected
  • >=2017.10.31_14 <2026.09.09
Fixed in
  • 2026.09.09

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 2026.09.09 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 this fixed version or later. Until patched, maintainers should be aware that MANIFEST.in exclusions are normalization-insensitive on macOS and consider additional manual checks to ensure sensitive files are not included.

Description

A Unicode normalization mismatch in setuptools' MANIFEST.in exclusion handling on macOS APFS/HFS+ filesystems causes excluded files with non-ASCII names to be included in source distributions. This occurs because setuptools matches file names byte-for-byte without Unicode normalization, leading to exclusion bypasses when the on-disk filename is in NFD form but the exclusion 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…