ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-xmj3-9gf7-h52w

setuptools: Windows path escape via namespace_packages.txt during legacy wheel installation Description

Published Oct 23, 2026 · catalog updated Oct 23, 2026 · setuptools: Windows path escape

Last checked Oct 24, 2026, 12 days ago.

Open the advisory

Exploitation likelihood is not on this record for GHSA-xmj3-9gf7-h52w. A missing EPSS score is not a low risk. Compare setuptools: Windows path escape with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (setuptools: Windows path escape).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Low—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
pip setuptools

### Summary On Windows, attacker-controlled content in a wheel's can cause setuptools' legacy wheel installation path to create an outside the requested . The attacker can influence the destination path, but not the contents of the created file. ### Details Tested setuptools commit: Relevant source: SHA-256: The relevant call path is: → → → A wheel can provide attacker-controlled content in: The namespace value is eventually used approximately as: markdown ### PoC The reproduction was performed entirely inside a disposable temporary directory. Layout: A synthetic wheel was created containing: whose content was the absolute path of: The real acquired setuptools implementation was then invoked: The operation completed without exception. Expected metadata was created under: but setuptools also created: The file did not exist before execution. Its contents were: The unrelated canary remained byte-identical. The sandbox was deleted after recording the evidence. ` outside the intended installation directory at a filesystem path influenced by the wheel, with the permissions of the process performing the installation. The demonstrated reproduction required the target parent directory to already exist.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • pip setuptools>= 38.2.2, < 84.1.0

How to fix GHSA-xmj3-9gf7-h52w

  • Upgrade

    GHSA-xmj3-9gf7-h52w lists a fix boundary at 84.1.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 84.1.0

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-xmj3-9gf7-h52w. A missing EPSS score is not a low risk. Compare setuptools: Windows path escape with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 38.2.2, < 84.1.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-22: Path Traversal. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Windows security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · GitHub Advisory Database

    Detected

    ### Summary On Windows, attacker-controlled content in a wheel's can cause setuptools' legacy wheel installation path to create an outside the requested . The attacker can influence the destination path, but not the contents of the created file. ### Details Tested setuptools commit: Relevant source: SHA-256: The relevant call path is: → → → A wheel can provide attacker-controlled content in: The n

  2. Oct 23, 2026 · GitHub Advisory Database

    Updated

    ### Summary On Windows, attacker-controlled content in a wheel's can cause setuptools' legacy wheel installation path to create an outside the requested . The attacker can influence the destination path, but not the contents of the created file. ### Details Tested setuptools commit: Relevant source: SHA-256: The relevant call path is: → → → A wheel can provide attacker-controlled content in: The n

Sources

  • GitHub Advisory DatabasePackage advisoryGHSA-xmj3-9gf7-h52w

    setuptools: Windows path escape via namespace_packages.txt during legacy wheel installation Description

    github.com

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseOct 24, 2026