@mborne/extract before 0.2.1 contains an OS command injection vulnerability that allows attackers to execute commands by supplying shell metacharacters in archivePath or targetDir options. Attackers controlling these values passed to extract() can inject commands into unquoted shelljs exec() strings in the unzip, 7z, tar-bz2 and gz extractors, running them with Node.js process privileges.
CVE-2026-110639
CRITICALPre-NVD 9.89.8Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-14. A secondary CVSS source baseline 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 60EG Risk 60/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)Severity98% × 45%The EG Score, 9.8 of 10.Exploitation2.7% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 2.7%
- EPSS %ILE
- 85th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (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
October 14, 2026
Last Modified
October 14, 2026
Advisory Details (5)
Auto-updated Oct 15, 2026Patch available. Sources: github_pr, github_release, github_commit.
Web page
@mborne/extract before 0.2.1 OS Command Injection via archivePath and targetDir | Advisories | VulnCheck
https://www.vulncheck.com/advisories/mborne-extract-before-0.2.1-os-command-injection-via-archivepath-and-targetdirGitHub release Patch Available
v0.2.1
Patch available: mborne/node-extract v0.2.1
https://github.com/mborne/node-extract/releases/tag/v0.2.1GitHub pull request Patch Available
fix: use safe discrete argument arrays for archive extractors (CWE-78)
Patch available: mborne/node-extract v0.2.1 (PR #8 merged 2026-10-13)
https://github.com/mborne/node-extract/pull/8GitHub commit Patch Available
commit 585e5b296573 (mborne/node-extract)
Patch available: mborne/node-extract v0.2.1 (contains commit 585e5b296573)
https://github.com/mborne/node-extract/commit/585e5b29657379e73c04f6f950ea8dc5319f8ae1Web page
node-extract/src/extractor/unzip.js at v0.2.0 · mborne/node-extract · GitHub
https://github.com/mborne/node-extract/blob/v0.2.0/src/extractor/unzip.js#L17-L19Vendor Advisories for CVE-2026-110639(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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.
- 2026-10-16 00:19 UTCEG score recompute
- 2026-10-16 00:18 UTCGHSA enrichmentGHSA-chf7-hjrj-qwh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 2.7% · 85th percentile
- 2026-10-14 18:25 UTCEG score recompute
- 2026-10-14 18:25 UTCGHSA enrichmentGHSA-chf7-hjrj-qwh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-14 17:50 UTCEG score recompute
- 2026-10-14 17:50 UTCGHSA enrichmentGHSA-chf7-hjrj-qwh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-14 15:28 UTCEG score recompute
- 2026-10-14 14:32 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
- 2026-10-14 14:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
Frequently asked(5)
What is CVE-2026-110639?
CVE-2026-110639 is a critical-severity vulnerability; its CVE record was published on October 14, 2026. @mborne/extract before 0.2.1 contains an OS command injection vulnerability that allows attackers to execute commands by supplying shell metacharacters in archivePath or targetDir options. Attackers controlling these values passed to extract() can inject commands into unquoted shelljs exec()…
When was CVE-2026-110639 made public?
CVE-2026-110639 was made public on September 2, 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 October 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-110639 actively exploited?
CVE-2026-110639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-110639?
CVE-2026-110639 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-110639?
A fix for CVE-2026-110639 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-110639 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-110639
Is Your Infrastructure Affected by CVE-2026-110639?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.