CVE-2026-130335 · Other
NO FIX YET
Info-ZIP Zip 3.0 and 3.1 beta through 3.1c pass filenames given to the -T option to the system C library call, which runs a shell. A filename containing shell metacharacters can make the shell run attacker-chosen commands on Linux and similar systems.
first public Nov 17, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Exposure needs the affected Zip version and a command line where an attacker controls the arguments, specifically a filename passed to -T. The sources state there is no known common scenario where an untrusted filename reaches a zip -T call, so most systems that run zip on trusted input can skip it. Systems that build zip commands from user-supplied filenames should review them.
Not affected if no-zip-t-usage, other-zip-version, trusted-input-only
Who cares linux, unix, zip
zip -v and compare the reported version with the affected range 3.0 and 3.1 beta through 3.1c.zip -T with filenames that come from users or outside input.No fix yet, per the sources.
Info-ZIP Zip 3.0 (and 3.1 beta through 3.1c) allows OS command injection by an attacker who controls the command line. The victim must use the -T option followed by a filename containing shell metacharacters, on a platform (such as Linux) where a suitable shell is run. This occurs because the system C library function is used. NOTE: there is no known common scenario in which an untrusted filename reaches a zip -T call.
This page as .md · .json · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.