Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.4.0, @zuke/cli uses lstat to inspect scaffold names but then performs link-following reads, writes, and permission changes in zuke setup and zuke import. An attacker who supplies an untrusted cloned repository, template, or archive with a symbolic link at a scaffolded name can cause setup to overwrite a target outside the selected directory with the invoking user's permissions. The .gitignore path requires no flag, while --force permits a linked launcher target to be written and made executable; import can also read link-target content and incorporate it into the generated build file. This issue is fixed in version 1.4.0.
CVE-2026-119291
MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd 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
Also known asEUVD-2026-114137 (ENISA EUVD)Source: ENISA EUVD
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMmedium confidence
- EG Risk
- 25EG Risk 25/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity55% × 45%Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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. - EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-04). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 30, 2026
Last Modified
November 4, 2026
Advisory Details (4)
Auto-updated Oct 30, 2026Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available
cli: v1.4.0
Patch available: zuke-build/zuke cli-v1.4.0
https://github.com/zuke-build/zuke/releases/tag/cli-v1.4.0GitHub commit Patch Available
commit 4257b0bc5ef5 (zuke-build/zuke)
Patch available: zuke-build/zuke prometheus-v1.1.1 (contains commit 4257b0bc5ef5)
https://github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654GitHub pull request Patch Available
feat(core): harden the registry launch, scaffold, spawn and workflow-gate paths
Patch available: zuke-build/zuke prometheus-v1.1.1 (PR #542 merged 2026-09-10)
https://github.com/zuke-build/zuke/pull/542GitHub advisoryMentions a patch (unverified)
zuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directory · Advisory · zuke-build/zuke · GitHub
https://github.com/zuke-build/zuke/security/advisories/GHSA-hc8w-3fgv-22pwWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 15× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-04 23:29 UTCEchelonGraph re-scored
- 2026-11-04 23:05 UTCEchelonGraph re-scored
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-30 17:02 UTCENISA EUVD ID recordedEUVD-2026-114137 · Source: ENISA EUVD
- 2026-10-30 16:28 UTCEchelonGraph re-scored
- 2026-10-30 16:00 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
- 2026-10-30 16:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-119291?
CVE-2026-119291 is a medium-severity vulnerability; its CVE record was published on October 30, 2026. Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.4.0, @zuke/cli uses lstat to inspect scaffold names but then performs link-following reads, writes, and permission changes in zuke setup and zuke import. An attacker who supplies an untrusted cloned repository,…
When was the CVE record for CVE-2026-119291 published?
The CVE record for CVE-2026-119291 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 4, 2026; the record at its source may have been updated since.
Is CVE-2026-119291 actively exploited?
CVE-2026-119291 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119291?
CVE-2026-119291 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119291?
A fix for CVE-2026-119291 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-119291
Is Your Infrastructure Affected by CVE-2026-119291?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.