<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-13T22:08:26.502714+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-115791</id>
    <title>CVE-2026-115791 — Prevent shadowing stdlib in gzip/tarfile/zipfile CLI during extraction</title>
    <updated>2026-11-13T22:08:26.504305+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Python Software Foundation CPython</p>
<p>When tarfile or zipfile command line interface (CLI) is used to</p>
<p>decompress an archive, a Python script shadowing the stdlib can be</p>
<p>created. Then if an error occurs during decompressing the next file,</p>
<p>the newly created Python script is executed. This is especially true</p>
<p>if the created Python is called traceback.py. The problem is that</p>
<p>Python adds the current directory to sys.path when python -m MODULE is</p>
<p>run, and the archive is also decompressed in the current directory.</p>
<p>The fix removes sys.path[0] in gzip, tarfile and zipfile command line</p>
<p>interface to prevent shadowing standard library modules from extracted</p>
<p>files.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-115791"/>
  </entry>
</feed>
