<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 15:44:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-59042 — PyInstaller has local privilege escalation vulnerability</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-59042</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pyinstaller&lt;/p&gt;
&lt;p&gt;PyInstaller bundles a Python application and all its dependencies into a single package. Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller &amp;lt; 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met. First, the application is built with PyInstaller &amp;lt; 6.0.0; both onedir and onefile mode are affected. Second, the optional bytecode encryption code feature was not enabled during the application build. Third, the attacker can create files/directories in the same directory where the executable is located. Fourth, the filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems). Fifth, the attacker is able to determine the offset at which the PYZ archive is embedded in the executable. The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller&amp;#39;s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pyinstaller&lt;/p&gt;
&lt;p&gt;PyInstaller bundles a Python application and all its dependencies into a single package. Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller &amp;lt; 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met. First, the application is built with PyInstaller &amp;lt; 6.0.0; both onedir and onefile mode are affected. Second, the optional bytecode encryption code feature was not enabled during the application build. Third, the attacker can create files/directories in the same directory where the executable is located. Fourth, the filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems). Fifth, the attacker is able to determine the offset at which the PYZ archive is embedded in the executable. The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller&amp;#39;s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-59042</guid>
    </item>
    <item>
      <title>GHSA-p2xp-xx3r-mffc — PyInstaller has local privilege escalation vulnerability</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-p2xp-xx3r-mffc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyinstaller&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller &amp;lt; 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met:&lt;/p&gt;
&lt;p&gt;1. Application is built with PyInstaller &amp;lt; 6.0.0; both onedir and onefile mode are affected.
2. Optional bytecode encryption code feature was **not** enabled during the application build.
3. The attacker can create files/directories in the same directory where the executable is located.
4. The filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems).
5. The attacker is able to determine the offset at which the PYZ archive is embedded in the executable.&lt;/p&gt;
&lt;p&gt;The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller&amp;#39;s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in the absence of the real, built-in module that is available when the bytecode-encryption feature is e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyinstaller&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller &amp;lt; 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met:&lt;/p&gt;
&lt;p&gt;1. Application is built with PyInstaller &amp;lt; 6.0.0; both onedir and onefile mode are affected.
2. Optional bytecode encryption code feature was **not** enabled during the application build.
3. The attacker can create files/directories in the same directory where the executable is located.
4. The filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems).
5. The attacker is able to determine the offset at which the PYZ archive is embedded in the executable.&lt;/p&gt;
&lt;p&gt;The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller&amp;#39;s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in the absence of the real, built-in module that is available when the bytecode-encryption feature is e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-p2xp-xx3r-mffc</guid>
    </item>
    <item>
      <title>PYSEC-2026-1813 — PyInstaller has local privilege escalation vulnerability</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-1813</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyinstaller&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller &amp;lt; 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met:&lt;/p&gt;
&lt;p&gt;1. Application is built with PyInstaller &amp;lt; 6.0.0; both onedir and onefile mode are affected.
2. Optional bytecode encryption code feature was **not** enabled during the application build.
3. The attacker can create files/directories in the same directory where the executable is located.
4. The filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems).
5. The attacker is able to determine the offset at which the PYZ archive is embedded in the executable.&lt;/p&gt;
&lt;p&gt;The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller&amp;#39;s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in the absence of the real, built-in module that is available when the bytecode-encryption feature is e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyinstaller&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to a special entry being appended to `sys.path` during the bootstrap process of a PyInstaller-frozen application, and due to the bootstrap script attempting to load an optional module for bytecode decryption while this entry is still present in `sys.path`, an application built with PyInstaller &amp;lt; 6.0.0 may be tricked by an unprivileged attacker into executing arbitrary python code when **all** of the following conditions are met:&lt;/p&gt;
&lt;p&gt;1. Application is built with PyInstaller &amp;lt; 6.0.0; both onedir and onefile mode are affected.
2. Optional bytecode encryption code feature was **not** enabled during the application build.
3. The attacker can create files/directories in the same directory where the executable is located.
4. The filesystem supports creation of files/directories that contain `?` in their name (i.e., non-Windows systems).
5. The attacker is able to determine the offset at which the PYZ archive is embedded in the executable.&lt;/p&gt;
&lt;p&gt;The attacker can create a directory (or a zip archive) next to the executable, with the name that matches the format used by PyInstaller&amp;#39;s bootloader to transmit information about the location of PYZ archive to the bootstrap script. If this directory (or zip archive) contains a python module whose name matches the name used by the optional bytecode encryption feature, this module will be loaded and executed by the bootstrap script (in the absence of the real, built-in module that is available when the bytecode-encryption feature is e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-1813</guid>
    </item>
  </channel>
</rss>
