https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 14:12:46 +0000 https://cve.radiocsirt.org/vuln/bit-libpython-2026-12003 <p><strong>Affected:</strong> Bitnami: libpython</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install.</p> <p>Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive.</p> <p>Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any es…</p> <p><strong>Affected:</strong> Bitnami: libpython</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install.</p> <p>Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive.</p> <p>Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any es…</p> https://cve.radiocsirt.org/vuln/bit-libpython-2026-12003 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0790 certfr-2026-avi-0790 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0790 https://cve.radiocsirt.org/vuln/euvd-2026-351834 EUVD-2026-351834 https://cve.radiocsirt.org/vuln/euvd-2026-351834 https://cve.radiocsirt.org/vuln/fkie_cve-2026-12003 <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install.</p> <p>Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive.</p> <p>Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any es…</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install.</p> <p>Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive.</p> <p>Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any es…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-12003 https://cve.radiocsirt.org/vuln/ghsa-2wqx-fp26-qh5v <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install.</p> <p>Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive.</p> <p>Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any es…</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install.</p> <p>Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive.</p> <p>Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any es…</p> https://cve.radiocsirt.org/vuln/ghsa-2wqx-fp26-qh5v https://cve.radiocsirt.org/vuln/msrc_cve-2026-12003 msrc_CVE-2026-12003 https://cve.radiocsirt.org/vuln/msrc_cve-2026-12003 https://cve.radiocsirt.org/vuln/oesa-2026-3070 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: python3</p> <p>Python combines remarkable power with very clear syntax. It has modules, classes, exceptions, very high level dynamic data types, and dynamic typing. There are interfaces to many system calls and libraries, as well as to various windowing systems. New built-in modules are easily written in C or C++ (or other languages, depending on the chosen implementation). Python is also usable as an extension language for applications written in other languages that need easy-to-use scripting or automation interfaces. Security Fix(es):</p> <p>When using the &amp;quot;configparser&amp;quot; module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value.(CVE-2026-0864)</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &amp;apos;PCbuild/&amp;apos;, the value of VPATH is set to &amp;apos;..\..&amp;apos;, which results in a landmark of &amp;apos;..\..\Modules\setup.local&amp;apos;. This path is outside the install directo…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: python3</p> <p>Python combines remarkable power with very clear syntax. It has modules, classes, exceptions, very high level dynamic data types, and dynamic typing. There are interfaces to many system calls and libraries, as well as to various windowing systems. New built-in modules are easily written in C or C++ (or other languages, depending on the chosen implementation). Python is also usable as an extension language for applications written in other languages that need easy-to-use scripting or automation interfaces. Security Fix(es):</p> <p>When using the &amp;quot;configparser&amp;quot; module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value.(CVE-2026-0864)</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree.</p> <p>On Windows, since builds are written to &amp;apos;PCbuild/&amp;apos;, the value of VPATH is set to &amp;apos;..\..&amp;apos;, which results in a landmark of &amp;apos;..\..\Modules\setup.local&amp;apos;. This path is outside the install directo…</p> https://cve.radiocsirt.org/vuln/oesa-2026-3070 https://cve.radiocsirt.org/vuln/rhsa-2026:67572 <p>python: Python unicodedata: Denial of Service due to excessive CPU consumption python: Python/Expat: Denial of Service via crafted XML document python: Python: FTP connection redirection via ftpcp() function bypass python: Python: Denial of Service via out-of-bounds write in BZ2 decompression python: Python: Privilege escalation due to insecure VPATH handling in Windows legacy installers python: Python tarfile module: Security filter bypass allows arbitrary file write</p> <p>python: Python unicodedata: Denial of Service due to excessive CPU consumption python: Python/Expat: Denial of Service via crafted XML document python: Python: FTP connection redirection via ftpcp() function bypass python: Python: Denial of Service via out-of-bounds write in BZ2 decompression python: Python: Privilege escalation due to insecure VPATH handling in Windows legacy installers python: Python tarfile module: Security filter bypass allows arbitrary file write</p> https://cve.radiocsirt.org/vuln/rhsa-2026:67572 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-12003 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: cython, Ubuntu:18.04:LTS: cython, Ubuntu:20.04:LTS: cython, Ubuntu:22.04:LTS: cython, Ubuntu:24.04:LTS: cython, Ubuntu:25.10: cython, Ubuntu:26.04:LTS: cython</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree. On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install. Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive. Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any escal…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: cython, Ubuntu:18.04:LTS: cython, Ubuntu:20.04:LTS: cython, Ubuntu:22.04:LTS: cython, Ubuntu:24.04:LTS: cython, Ubuntu:25.10: cython, Ubuntu:26.04:LTS: cython</p> <p>To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree. On Windows, since builds are written to &#39;PCbuild/&#39;, the value of VPATH is set to &#39;..\..&#39;, which results in a landmark of &#39;..\..\Modules\setup.local&#39;. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install. Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive. Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any escal…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-12003 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1971 <p>Ein Angreifer kann mehrere Schwachstellen in CPython ausnutzen, um Dateien zu manipulieren und um einen Denial-of-Service-Zustand auszulösen</p> <p>Ein Angreifer kann mehrere Schwachstellen in CPython ausnutzen, um Dateien zu manipulieren und um einen Denial-of-Service-Zustand auszulösen</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1971