<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T08:53:22.727468+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2019-16784</id>
    <title>CVE-2019-16784 — Local Privilege Escalation present only on the Windows version of PyInstaller</title>
    <updated>2026-10-02T08:53:22.774688+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyInstaller</p>
<p>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 "onefile" mode is launched by a privileged user (at least more than the current one) which have his "TempPath" 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).</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2019-16784"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-7fcj-pq9j-wh2r</id>
    <title>GHSA-7fcj-pq9j-wh2r — Local Privilege Escalation in PyInstaller</title>
    <updated>2026-10-02T08:53:22.774843+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: PyInstaller</p>
<p>### Impact</p>
<p>Local Privilege Escalation in all Windows software frozen by PyInstaller in "onefile" mode.</p>
<p>The vulnerability is present only on Windows and in this particular case: If a **software frozen by PyInstaller in "onefile" mode** is launched by a (privileged) user who has **his/her "TempPath" 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).</p>
<p>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).</p>
<p>While PyInstaller itself was not vulnerable, all Windows software frozen by PyInstaller in "onefile" mode is vulnerable.</p>
<p>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</p>
<p>Affected
- all Windows software frozen by PyInstaller in "onefile" mode</p>
<p>No affected
- PyInstaller itself (except if frozen by PyInstaller in "onefile" mode on Windows)
- software frozen in "one*dir*" mode
- other platforms (GNU/Linux, OS X, BSD, etc.)</p>
<p>### 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.</p>
<p>### Workarounds
There is no known workaround. Users using PyI…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-7fcj-pq9j-wh2r"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2020-175</id>
    <title>PYSEC-2020-175</title>
    <updated>2026-10-02T08:53:22.774950+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pyinstaller</p>
<p>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 "onefile" mode is launched by a privileged user (at least more than the current one) which have his "TempPath" 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).</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2020-175"/>
  </entry>
</feed>
