Is CVE-2026-80427 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-80427 being exploited in the wild.

How severe is CVE-2026-80427?

High severity, with a CVSS score of 8.4, published 26 August 2026.

Which products and versions are affected?

nfriedly bestzip before 2.2.6 and 3.0.2 (specifically 3.0.0, 3.0.1 and earlier versions).

Is there a fix for CVE-2026-80427?

A patch was published on 2026-08-07: Versions 2.2.6 and 3.0.2 released with fix adding -- delimiter Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-80427 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-80427?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-80427: bestzip argument injection in native zip execution

CVE-2026-80427 · Severity: high · CVSS 8.4 · Published 2026-08-26

bestzip is a Node.js wrapper around the system's native zip utility used to create compressed archives. An attacker who can control input file paths can inject special command-line flags that cause zip to execute arbitrary system commands, leading to complete host compromise and data theft. This affects any application that passes user-supplied or untrusted file names to bestzip.

Quick answers

Is CVE-2026-80427 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-80427 being exploited in the wild.
How severe is CVE-2026-80427?: High severity, with a CVSS score of 8.4, published 26 August 2026.
Which products and versions are affected?: nfriedly bestzip before 2.2.6 and 3.0.2 (specifically 3.0.0, 3.0.1 and earlier versions).
Is there a fix for CVE-2026-80427?: A patch was published on 2026-08-07: Versions 2.2.6 and 3.0.2 released with fix adding -- delimiter Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-80427 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-80427?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

bestzip constructs an argument array for the native zip command without inserting the -- delimiter between the destination archive and source file paths. This allows arguments starting with a hyphen to be interpreted as command-line options rather than file names. An attacker can supply crafted source file names such as "-T" (test archive) and "-TT <command>" (specify test command) to cause zip to execute arbitrary shell commands with the privileges of the Node.js process. The vulnerability affects versions prior to 2.2.6 and 3.0.2, which add the explicit -- separator. Attack requires no privileges or user interaction and is exploitable by local or networked attackers who can influence file path inputs.

Affected products

nfriedly bestzip before 2.2.6 and 3.0.2 (specifically 3.0.0, 3.0.1 and earlier versions)

Timeline

2026-08-26: disclosed: CVE-2026-80427 published and GitHub security advisory GHSA-p87m-9567-rgcc released
2026-08-07: patched: Versions 2.2.6 and 3.0.2 released with fix adding -- delimiter

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.