CVE-2026-115791 · Runtime
NO FIX YET
When the tarfile or zipfile command line tool extracts an archive, a file it writes into the current directory can shadow a standard library module such as traceback.py. If a later extraction step fails, Python imports and runs that planted script.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Exposure needs someone to run the tarfile, zipfile or gzip command line interface on an untrusted archive from a directory that holds other files. The Python interpreter's sys.path behavior makes the current directory importable under python -m. Programs that import these modules as a library, or extract archives only from trusted sources in an empty directory, are less exposed.
Not affected if empty-working-directory, library-use-only, trusted-archives
Who cares archives, cli, python
python3 --version and compare with the fixed versions in the product ranges, if the sources list thempython -m tarfile, python -m zipfile or python -m gzip to extract untrusted archives in a working directoryUnknown from the sources.
When tarfile or zipfile command line interface (CLI) is used to
decompress an archive, a Python script shadowing the stdlib can be
created. Then if an error occurs during decompressing the next file,
the newly created Python script is executed. This is especially true
if the created Python is called traceback.py. The problem is that
Python adds the current directory to sys.path when python -m MODULE is
run, and the archive is also decompressed in the current directory.
The fix removes sys.path[0] in gzip, tarfile and zipfile command line
interface to prevent shadowing standard library modules from extracted
files.
This page as .md ·
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.