CVE-2026-114105: Adm-zip before 0.6.1 Privilege Escalation via keepOriginalPermission Setuid Bits
Adm-zip before 0.6.1 contains an incorrect permission assignment vulnerability that allows attackers to set setuid, setgid, or sticky bits on extracted files when keepOriginalPermission is enabled. Attackers can craft zip external file attributes that pass unmasked into chmod, letting attacker-controlled executables gain elevated privileges when extracted as root and later run.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
adm-zipto a version that resolves this vulnerability.Fixed in 0.6.1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Systems using npm/adm-zip before 0.6.1 are exposed when they extract attacker-controlled ZIP archives with keepOriginalPermission enabled. The practical impact requires extraction to occur as root and for an extracted attacker-controlled executable to later be run.
What does an attacker need to exploit it?
An attacker needs to provide a crafted ZIP archive whose external file attributes include setuid, setgid, or sticky permission bits. They do not need prior privileges or user interaction according to the supplied vector, but the archive must be processed by the vulnerable extraction path.
Is the default configuration affected?
The vulnerable behavior is specifically tied to keepOriginalPermission being enabled. The provided information does not indicate that extraction with this option disabled is affected.
What can be done before updating?
Do not enable keepOriginalPermission when extracting untrusted archives, and avoid extracting such archives as root. Restrict execution of files extracted from untrusted ZIP archives until the dependency can be updated to 0.6.1 or later.