<?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://db.gcve.eu</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, 13 Nov 2026 22:08:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-115791 — Prevent shadowing stdlib in gzip/tarfile/zipfile CLI during extraction</title>
      <link>https://db.gcve.eu/vuln/cve-2026-115791</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Python Software Foundation CPython&lt;/p&gt;
&lt;p&gt;When tarfile or zipfile command line interface (CLI) is used to&lt;/p&gt;
&lt;p&gt;decompress an archive, a Python script shadowing the stdlib can be&lt;/p&gt;
&lt;p&gt;created. Then if an error occurs during decompressing the next file,&lt;/p&gt;
&lt;p&gt;the newly created Python script is executed. This is especially true&lt;/p&gt;
&lt;p&gt;if the created Python is called traceback.py. The problem is that&lt;/p&gt;
&lt;p&gt;Python adds the current directory to sys.path when python -m MODULE is&lt;/p&gt;
&lt;p&gt;run, and the archive is also decompressed in the current directory.&lt;/p&gt;
&lt;p&gt;The fix removes sys.path[0] in gzip, tarfile and zipfile command line&lt;/p&gt;
&lt;p&gt;interface to prevent shadowing standard library modules from extracted&lt;/p&gt;
&lt;p&gt;files.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Python Software Foundation CPython&lt;/p&gt;
&lt;p&gt;When tarfile or zipfile command line interface (CLI) is used to&lt;/p&gt;
&lt;p&gt;decompress an archive, a Python script shadowing the stdlib can be&lt;/p&gt;
&lt;p&gt;created. Then if an error occurs during decompressing the next file,&lt;/p&gt;
&lt;p&gt;the newly created Python script is executed. This is especially true&lt;/p&gt;
&lt;p&gt;if the created Python is called traceback.py. The problem is that&lt;/p&gt;
&lt;p&gt;Python adds the current directory to sys.path when python -m MODULE is&lt;/p&gt;
&lt;p&gt;run, and the archive is also decompressed in the current directory.&lt;/p&gt;
&lt;p&gt;The fix removes sys.path[0] in gzip, tarfile and zipfile command line&lt;/p&gt;
&lt;p&gt;interface to prevent shadowing standard library modules from extracted&lt;/p&gt;
&lt;p&gt;files.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-115791</guid>
    </item>
  </channel>
</rss>
