CVE-2026-59890: Unicode normalization exclusion bypass in setuptools
- Vendor
- Python
setuptools versions before 83.0.0 contain a Unicode normalization flaw in FileList processing during source-distribution creation. The exclude, global-exclude, recursive-exclude, and prune directives match compiled glob patterns against on-disk filenames without Unicode normalization. On macOS APFS or HFS+, a filename in Unicode Normalization Form D (NFD) can therefore evade an exclusion pattern written in Normalization Form C (NFC), causing an intended exclusion to fail and the file to enter the source distribution. Pure-ASCII exclusion rules are not affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Files intended to remain outside a source distribution can be silently packaged and subsequently disclosed when the artifact is shared or published. Exposed material may include secrets, private configuration, or confidential test fixtures. Publication to a public package index can make disclosure effectively irreversible. The vulnerability also undermines the integrity of packaging exclusion policies; direct code execution or availability impact is not established.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid relying on non-ASCII exclusion patterns on macOS APFS or HFS+. Use ASCII-only names for excluded files and directories where practical, or build source distributions using a verified workflow that avoids NFC/NFD mismatches. Inspect generated archives before publishing and confirm that sensitive files are absent.
Remediation
Patch, then assume compromise.
Upgrade setuptools to version 83.0.0 or later, or install the applicable vendor-provided package update containing the fix. The fix normalizes file paths and exclusion patterns to a common Unicode form before matching.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-59890 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-59890 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-59890?
- Yes. As of Nov 17, 2026, Mallory has reports of a public exploit for CVE-2026-59890.
- Is there a patch for CVE-2026-59890?
- Upgrade setuptools to version 83.0.0 or later, or install the applicable vendor-provided package update containing the fix. The fix normalizes file paths and exclusion patterns to a common Unicode form before matching.
- What products are affected by CVE-2026-59890?
- Python Setuptools.
- How severe is CVE-2026-59890?
- CVE-2026-59890 has a CVSS v3.1 score of 6.1 (Medium) and an EPSS score of 0.53% (45th percentile) as of Nov 17, 2026.
Recent activity
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.