sdist · setuptools: MANIFEST.in exclusion bypass
Affects neovim-remoteSource GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 2.5.1_5 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.1_5
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 neovim-remote to 2.5.1_5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewneovim-remotepkg:brew/neovim-remoteOther threats | Affected
| Fixed in
|
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.5.1_5 that normalizes both the MANIFEST.in patterns and the on-disk filenames to a canonical Unicode form before matching. Users should upgrade to this fixed version or later. Until upgraded, maintainers should be aware that MANIFEST.in exclusions for non-ASCII filenames may not work correctly on macOS filesystems and consider alternative methods to protect sensitive files.
Description
A Unicode normalization mismatch in setuptools' handling of MANIFEST.in exclusion rules on macOS APFS/HFS+ filesystems can cause excluded files with non-ASCII names to be mistakenly included in source distributions. This occurs because the file matching is done byte-for-byte without Unicode normalization, allowing files named with decomposed Unicode (NFD) to bypass exclusion rules written in composed form (NFC). This can lead to unintended disclosure of sensitive files when publishing to PyPI.
References
- github.com/pypa/setuptools/security/advisories/GHSA-h35f-9h28-mq5c (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-59890 (opens in a new tab)
- github.com/pypa/setuptools/commit/dd9f436a36486b4cb8a4c70a2321548b0be09b8f (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/setuptools/PYSEC-2026-3447.yaml (opens in a new tab)
- github.com/pypa/setuptools (opens in a new tab)
- github.com/pypa/setuptools/releases/tag/v83.0.0 (opens in a new tab)