← Back
CVE-2026-59890
medium
CVSS 6.1
Vulnerability in setuptools (CVE-2026-59890)
Summary
vulnerability in setuptools (CVE-2026-59890). Confidential information can be exposed externally. Exploitable via ``FileList``. Mitigation: upgrade to `83.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59890** has been found in setuptools.
Attackers can target a specific entry point like ``FileList`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.1/10.
What to do: upgrade setuptools to **83.0.0** or later.
If unsure, ask your IT team or search "setuptools CVE-2026-59890" on the vendor's site.
CVE-2026-59890 (setuptools) — CWE-176 / CVSS v3 6.1
Attack vector: local / unauthenticated
Attack surface: `FileList` / `MANIFEST.in` / `exclude` / `prune`
Patched: `83.0.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-176) exists in setuptools. Attackers reach the vulnerable code path via ``FileList`` without authentication.
📍 Affected scope
setuptools — . Attack surface: `FileList` / `MANIFEST.in` / `exclude` / `prune`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **83.0.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'setuptools' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'setuptools' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `setuptools` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade setuptools to 83.0.0ステージング環境で 83.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
setuptools
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"83.0.0"}]}]
References
- web https://github.com/pypa/setuptools/commit/dd9f436a36486b4cb8a4c70a2321548b0be09b8f
- web https://github.com/pypa/setuptools/releases/tag/v83.0.0
- web https://github.com/pypa/setuptools/security/advisories/GHSA-h35f-9h28-mq5c
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59890
- web https://github.com/pypa/advisory-database/tree/main/vulns/setuptools/PYSEC-2026-3447.yaml
- web https://github.com/advisories/GHSA-h35f-9h28-mq5c