Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-59890: Unicode normalization exclusion bypass in setuptools

Published Jul 8, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days9 mentions · peak 3 in a dayToday
CVSS6.1Medium · v3.1
EPSS0.53%45th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Python
IdentifiersCVE-2026-59890CWE-176 · Improper Handling of Unicode…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
PythonSetuptoolsapplication
FAQ

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.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cyber security newsNews · Nov 17, 2026Hackers Exploit macOS ß vs ss Filename Trick to Bypass Developer Tool Security ChecksPython setuptools versions before 83.0.0 fail to normalize filenames when applying MANIFEST.in exclusion directives. On APFS or HFS+, filenames in NFD form can bypass exclusions written in NFC form, causing excluded files to enter source distributions. Version 83.0.0 fixes the vulnerability.Read more ↗cryptika blogNews · Nov 17, 2026Hackers Exploit macOS ß vs ss Filename Trick to Bypass Developer Tool Security Checks | Cryptika CybersecurityPython setuptools versions before 83.0.0 can fail to apply MANIFEST.in exclusions when filenames and exclusion patterns use different Unicode normalization forms on APFS or HFS+. Excluded files can enter source distributions, potentially exposing sensitive information. Version 83.0.0 fixes the flaw.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.12.1 : python-setuptools (EulerOS-SA-... | Tenable®A vulnerability associated with python-setuptools and python3-setuptools in EulerOS Virtualization 2.12.1. The listed CVSS vector indicates local access and required user interaction, with high confidentiality impact and low integrity impact. Exploits and a patch are available; the excerpt does not describe the underlying flaw.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.12.0 : python-setuptools (EulerOS-SA-... | Tenable®A vulnerability affecting python-setuptools and python3-setuptools in EulerOS Virtualization 2.12.0. The listed CVSS v3 vector indicates local exploitation requiring user interaction, with high confidentiality impact and low integrity impact. Exploits and patches are available; the excerpt does not describe the underlying flaw.Read more ↗
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.