<?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>Fri, 02 Oct 2026 08:52:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-16784 — Local Privilege Escalation present only on the Windows version of PyInstaller</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2019-16784</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyInstaller&lt;/p&gt;
&lt;p&gt;In PyInstaller before version 3.6, only on Windows, a local privilege escalation vulnerability is present in this particular case: If a software using PyInstaller in &amp;#34;onefile&amp;#34; mode is launched by a privileged user (at least more than the current one) which have his &amp;#34;TempPath&amp;#34; resolving to a world writable directory. This is the case for example if the software is launched as a service or as a scheduled task using a system account (TempPath will be C:\Windows\Temp). In order to be exploitable the software has to be (re)started after the attacker launch the exploit program, so for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyInstaller&lt;/p&gt;
&lt;p&gt;In PyInstaller before version 3.6, only on Windows, a local privilege escalation vulnerability is present in this particular case: If a software using PyInstaller in &amp;#34;onefile&amp;#34; mode is launched by a privileged user (at least more than the current one) which have his &amp;#34;TempPath&amp;#34; resolving to a world writable directory. This is the case for example if the software is launched as a service or as a scheduled task using a system account (TempPath will be C:\Windows\Temp). In order to be exploitable the software has to be (re)started after the attacker launch the exploit program, so for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2019-16784</guid>
    </item>
    <item>
      <title>GHSA-7fcj-pq9j-wh2r — Local Privilege Escalation in PyInstaller</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-7fcj-pq9j-wh2r</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;Local Privilege Escalation in all Windows software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode.&lt;/p&gt;
&lt;p&gt;The vulnerability is present only on Windows and in this particular case: If a **software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode** is launched by a (privileged) user who has **his/her &amp;#34;TempPath&amp;#34; resolving to a world writable directory**. This is the case e.g. if the software is launched as a service or as a scheduled task using a system account (in which case TempPath will default to C:\Windows\Temp).&lt;/p&gt;
&lt;p&gt;In order to be exploitable the software has to be (re)started after the attacker has launched the exploit program. So for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).&lt;/p&gt;
&lt;p&gt;While PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode is vulnerable.&lt;/p&gt;
&lt;p&gt;CVSSv3 score 7.0 (High)
CVSSv3 vector CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H&lt;/p&gt;
&lt;p&gt;Affected
- all Windows software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode&lt;/p&gt;
&lt;p&gt;No affected
- PyInstaller itself (except if frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode on Windows)
- software frozen in &amp;#34;one*dir*&amp;#34; mode
- other platforms (GNU/Linux, OS X, BSD, etc.)&lt;/p&gt;
&lt;p&gt;### Patches
The problem is patched in commits 42a67148b3bdf9211fda8499fdc5b63acdd7e6cc (fixed code) and be948cf0954707671aa499da17b10c86b6fa5e5c (recompiled bootloaders). Users should upgrade to PyInstaller version 3.6 and rebuild their software.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no known workaround. Users using PyI…&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;Local Privilege Escalation in all Windows software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode.&lt;/p&gt;
&lt;p&gt;The vulnerability is present only on Windows and in this particular case: If a **software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode** is launched by a (privileged) user who has **his/her &amp;#34;TempPath&amp;#34; resolving to a world writable directory**. This is the case e.g. if the software is launched as a service or as a scheduled task using a system account (in which case TempPath will default to C:\Windows\Temp).&lt;/p&gt;
&lt;p&gt;In order to be exploitable the software has to be (re)started after the attacker has launched the exploit program. So for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).&lt;/p&gt;
&lt;p&gt;While PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode is vulnerable.&lt;/p&gt;
&lt;p&gt;CVSSv3 score 7.0 (High)
CVSSv3 vector CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H&lt;/p&gt;
&lt;p&gt;Affected
- all Windows software frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode&lt;/p&gt;
&lt;p&gt;No affected
- PyInstaller itself (except if frozen by PyInstaller in &amp;#34;onefile&amp;#34; mode on Windows)
- software frozen in &amp;#34;one*dir*&amp;#34; mode
- other platforms (GNU/Linux, OS X, BSD, etc.)&lt;/p&gt;
&lt;p&gt;### Patches
The problem is patched in commits 42a67148b3bdf9211fda8499fdc5b63acdd7e6cc (fixed code) and be948cf0954707671aa499da17b10c86b6fa5e5c (recompiled bootloaders). Users should upgrade to PyInstaller version 3.6 and rebuild their software.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no known workaround. Users using PyI…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-7fcj-pq9j-wh2r</guid>
    </item>
    <item>
      <title>PYSEC-2020-175</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2020-175</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyinstaller&lt;/p&gt;
&lt;p&gt;In PyInstaller before version 3.6, only on Windows, a local privilege escalation vulnerability is present in this particular case: If a software using PyInstaller in &amp;#34;onefile&amp;#34; mode is launched by a privileged user (at least more than the current one) which have his &amp;#34;TempPath&amp;#34; resolving to a world writable directory. This is the case for example if the software is launched as a service or as a scheduled task using a system account (TempPath will be C:\Windows\Temp). In order to be exploitable the software has to be (re)started after the attacker launch the exploit program, so for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyinstaller&lt;/p&gt;
&lt;p&gt;In PyInstaller before version 3.6, only on Windows, a local privilege escalation vulnerability is present in this particular case: If a software using PyInstaller in &amp;#34;onefile&amp;#34; mode is launched by a privileged user (at least more than the current one) which have his &amp;#34;TempPath&amp;#34; resolving to a world writable directory. This is the case for example if the software is launched as a service or as a scheduled task using a system account (TempPath will be C:\Windows\Temp). In order to be exploitable the software has to be (re)started after the attacker launch the exploit program, so for a service launched at startup, a service restart is needed (e.g. after a crash or an upgrade).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2020-175</guid>
    </item>
  </channel>
</rss>
