CVE-2026-80427

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists nfriedly bestzip versions before 2.2.6 and 3.0.0 up to but not including 3.0.2 as affected. No release containing a fix is confirmed on record.

bestzip builds the argument list for the system zip utility without separating options from operands. The destination archive path and the caller-supplied source paths are passed to the child process with no -- delimiter between them, so any source entry beginning with a hyphen is interpreted by zip as an option rather than a file name. zip accepts -T to test the finished archive and -TT to name the command used to perform that test, so a source list containing those two entries and a command string causes zip to run that command through a shell once the archive has been written. An application that passes a file name or path it received from an untrusted source into the bestzip API therefore executes a command of the supplier's choosing. Versions 2.2.6 and 3.0.2 add the delimiter.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
The EG Score, 8.4 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Aug 26, 2026
No fix on record yet. Sources: github.
Web page

bestzip before 2.2.6 and 3.0.x before 3.0.2 Argument Injection via Missing Option Delimiter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/bestzip-before-2.2.6-and-3.0-x-before-3.0.2-argument-injection-via-missing-option-delimiter
GitHub advisoryMentions a patch (unverified)

Argument Injection in bestzip via native zip CLI execution · Advisory · nfriedly/node-bestzip · GitHub

https://github.com/nfriedly/node-bestzip/security/advisories/GHSA-p87m-9567-rgcc
Web page

GitHub - nfriedly/node-bestzip: Provides a `bestzip` command that uses the system `zip` if avaliable, and a Node.js implimentation otherwise. · GitHub

https://github.com/nfriedly/node-bestzip

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 95 are merged into the row they repeat.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-13 06:30 UTCEG score recompute
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-12 14:57 UTCEG score recompute
  5. 2026-10-11 19:21 UTCEG score recompute
  6. 2026-10-11 16:37 UTCEG score recompute
  7. 2026-10-11 13:55 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-10 06:06 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-09 03:22 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-08 01:51 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-06 23:41 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-06 01:41 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-05 01:38 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-03 16:06 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-03 04:56 UTCEG score recompute
  25. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 67 more
  1. 2026-10-01 19:55 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-09-30 19:58 UTCEG score recompute
  4. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-09-30 06:03 UTCEG score recompute
  6. 2026-09-29 08:20 UTCEG score recompute
  7. 2026-09-28 21:20 UTCEG score recompute
  8. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-09-27 18:35 UTCEG score recompute
  10. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-09-26 20:35 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-09-24 21:14 UTCEG score recompute
  15. 2026-09-24 18:48 UTCEG score recompute
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-09-23 19:58 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-09-22 21:59 UTCEG score recompute
  20. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-21 23:58 UTCEG score recompute
  22. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-21 01:58 UTCEG score recompute
  24. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-19 16:58 UTCEG score recompute
  26. 2026-09-19 05:57 UTCEG score recompute
  27. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-17 20:57 UTCEG score recompute
  29. 2026-09-16 21:55 UTCEG score recompute
  30. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-16 10:55 UTCEG score recompute
  32. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-15 12:55 UTCEG score recompute
  34. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-13 16:55 UTCEG score recompute
  36. 2026-09-12 18:55 UTCEG score recompute
  37. 2026-09-11 20:56 UTCEG score recompute
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-09-11 09:55 UTCEG score recompute
  40. 2026-09-10 11:55 UTCEG score recompute
  41. 2026-09-09 00:48 UTCEG score recompute
  42. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  43. 2026-09-07 17:41 UTCEG score recompute
  44. 2026-09-06 19:40 UTCEG score recompute
  45. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  46. 2026-09-05 21:37 UTCEG score recompute
  47. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  48. 2026-09-04 23:35 UTCEG score recompute
  49. 2026-09-04 11:24 UTCEG score recompute
  50. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  51. 2026-09-02 15:10 UTCEG score recompute
  52. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  53. 2026-09-01 17:07 UTCEG score recompute
  54. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  55. 2026-08-30 21:00 UTCEG score recompute
  56. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  57. 2026-08-30 09:59 UTCEG score recompute
  58. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  59. 2026-08-29 11:59 UTCEG score recompute
  60. 2026-08-29 00:27 UTCEG score recompute
  61. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  62. 2026-08-27 15:25 UTCEG score recompute
  63. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  64. 2026-08-26 17:21 UTCEG score recompute
  65. 2026-08-26 16:22 UTCEG score recompute
  66. 2026-08-26 15:55 UTCEG score recomputeFirst assessed: 8.4 HIGH
  67. 2026-08-26 15:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80427?
CVE-2026-80427 is a high-severity vulnerability; its CVE record was published on August 26, 2026. bestzip builds the argument list for the system zip utility without separating options from operands. The destination archive path and the caller-supplied source paths are passed to the child process with no -- delimiter between them, so any source entry beginning with a hyphen is interpreted by…
When was CVE-2026-80427 made public?
CVE-2026-80427 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-80427 actively exploited?
CVE-2026-80427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80427?
CVE-2026-80427 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80427?
No fix for CVE-2026-80427 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists nfriedly bestzip versions before 2.2.6 and 3.0.0 up to but not including 3.0.2 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80427

Explore →

Is Your Infrastructure Affected by CVE-2026-80427?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs