A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The file content is fixed and the path is attacker-controlled but requires the target directory to preexist.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's .dist-info/namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The created file has fixed content and is placed at a filesystem path influenced by the wheel, with the permissions of the installing process. The attack requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's .dist-info/namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because an absolute Windows path in the namespace_packages.txt is not properly validated, leading to path escape during installation. The created __init__.py file contains fixed content and is created with the permissions of the installing process. The parent directory must already exist for this to succeed.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with a specially crafted namespace_packages.txt that causes the legacy wheel installation process to create an __init__.py file outside the intended installation directory. This file has fixed content and is created with the permissions of the installing process. The attack requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with a specially crafted .dist-info/namespace_packages.txt file. This can cause setuptools' legacy wheel installation to create an __init__.py file outside the intended installation directory at an attacker-influenced absolute path. The created file contains fixed content and is created with the permissions of the installing process. The vulnerability requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's .dist-info/namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The created file has fixed content and is placed at a filesystem path influenced by the wheel, with the permissions of the installing process. The target parent directory must already exist for this to occur.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with malicious content in the namespace_packages.txt metadata. This can cause setuptools' legacy wheel installation to create an __init__.py file outside the intended installation directory at an attacker-influenced absolute path. The created file contains fixed content and the operation requires the target directory to preexist. This flaw is patched in setuptools version 2026.10.8_1.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because an absolute Windows path in namespace_packages.txt is not properly validated, enabling path escape. The created file contains fixed content and is written with the installer's permissions. The issue requires the target directory to pre-exist.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with a specially crafted namespace_packages.txt that causes setuptools to create an __init__.py file outside the intended installation directory. This file is created at an attacker-influenced absolute path with fixed content and the permissions of the installing process. The issue arises because the path in namespace_packages.txt is not properly validated and can override the base installation path due to Windows path handling. The vulnerability requires the target directory to already exist and does not allow control over the file contents.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with malicious content in the namespace_packages.txt metadata. This can cause setuptools' legacy wheel installation to create an __init__.py file outside the intended installation directory, at a path influenced by the attacker. The created file contains fixed content and the operation requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's .dist-info/namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This file is created at a filesystem path influenced by the wheel content, with the permissions of the installing process. The created __init__.py contains fixed content and the attack requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause creation of an __init__.py file outside the intended installation directory. This occurs because the path from namespace_packages.txt can be interpreted as an absolute Windows path, bypassing intended directory restrictions. The created file has fixed content and is created with the installer's permissions. The issue requires the target directory to preexist.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's .dist-info/namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This file has fixed content and is created with the permissions of the installing process. The issue arises because an absolute Windows path in the namespace_packages.txt is not properly validated, enabling path escape during installation.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because the path in namespace_packages.txt can be an absolute Windows path, which setuptools uses without proper validation, leading to file creation at an attacker-influenced location. The created file has fixed content and the permissions of the installing process. The issue affects setuptools versions from 2.1.0_5 up to but not including 2.1.0_22 and is fixed in 2.1.0_22.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt file to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because an absolute Windows path in namespace_packages.txt is improperly handled, leading to file creation at an attacker-influenced location with the installer's permissions. The created __init__.py file contains fixed content. The issue requires the target directory to pre-exist.
A vulnerability in setuptools on Windows allows a crafted wheel file to cause the creation of an __init__.py file outside the intended installation directory during legacy wheel installation. This occurs because the namespace_packages.txt file can specify an absolute Windows path that overrides the destination directory. The created file has fixed content and is written with the permissions of the installing process. The parent directory must already exist for this to succeed.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with a specially crafted .dist-info/namespace_packages.txt that causes setuptools' legacy wheel installation to create an __init__.py file outside the intended installation directory. This file has fixed content and is created with the permissions of the installing process. The attack requires the target directory to pre-exist and does not allow control over the file contents.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel containing a namespace_packages.txt file with an absolute path. During legacy wheel installation, this can cause setuptools to create an __init__.py file outside the intended installation directory. The created file has fixed content and is placed at a filesystem path influenced by the attacker, with the permissions of the installing process. The parent directory must already exist for this to occur. This issue affects setuptools versions from 0.26.0 up to but not including 0.35.0 and is fixed in version 0.35.0.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt file to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The attacker can control the destination path of this file but not its contents. This occurs because an absolute Windows path in namespace_packages.txt is improperly handled, leading to path escape during installation.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because an absolute Windows path in namespace_packages.txt is used without proper validation, enabling path escape. The created file contains fixed content and is created with the permissions of the installing process. The issue affects setuptools versions >=3.1.0 and <3.2.0_1 and requires the target parent directory to already exist.