CVE-2026-59160

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-78834 (ENISA EUVD) · GHSA-2r5q-h53f-9rp3 (GitHub Security Advisories)Source: ENISA EUVD

8.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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Yeger is a monorepo for npm packages maintained under the yeger scope. Prior to 2.8.9, the turbo-graph package starts its embedded Next.js server from packages/turbo-graph/src/index.ts on all interfaces, including 0.0.0.0:29312 by default, while the GET handler for /api/run in packages/turbo-graph-ui/app/api/run/route.ts has no authentication, authorization, CSRF protection, or task allowlist. The handler accepts the tasks, filter, and force query parameters, and buildResponseFromArgs passes attacker-selected task names to spawn() as Turbo CLI arguments. An adjacent-network attacker can execute any task defined in the victim repository's turbo.json with the privileges of the developer OS user, potentially exposing secrets, modifying files or infrastructure, or causing destructive availability effects. The use of an argument array prevents traditional shell metacharacter injection but does not prevent unauthorized execution of defined tasks. This issue is fixed in version 2.8.9.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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: 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
0.5%
EPSS %ILE
41st
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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.

The score's inputs: 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

September 9, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit a6c41db6b575 (DerYeger/yeger)

Patch available: DerYeger/yeger @yeger/turbo-graph@2.8.9 (contains commit a6c41db6b575)

https://github.com/DerYeger/yeger/commit/a6c41db6b575cccdd8ff89dbe8ce1792ad062852
GitHub advisoryMentions a patch (unverified)

Unauthenticated Network-Exposed Turborepo Task Execution via /api/run · Advisory · DerYeger/yeger · GitHub

https://github.com/DerYeger/yeger/security/advisories/GHSA-2r5q-h53f-9rp3

Vendor Advisories for CVE-2026-59160(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@yeger/turbo-graph @ 2.8.12 (fixes <= 2.8.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@yeger/turbo-graph—
  • every version up to 2.8.12: fixed in 2.8.12
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 49× 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.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 07:42 UTCGHSA enrichmentGHSA-2r5q-h53f-9rp3 · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-01 07:42 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-27 18:53 UTCEG score recompute
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 14:16 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-20 09:42 UTCEG score recompute
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-18 03:27 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 58 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-13 16:18 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-12 15:53 UTCEG score recompute
  5. 2026-10-11 19:36 UTCEG score recompute
  6. 2026-10-11 16:51 UTCEG score recompute
  7. 2026-10-11 14:14 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-10 20:14 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-10 08:16 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-08 23:55 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-08 08:00 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-06 19:20 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-05 19:25 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-05 07:18 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-03 19:18 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-02 19:23 UTCEG score recompute
  26. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-10-02 07:25 UTCEG score recompute
  28. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-30 18:09 UTCEG score recompute
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-09-30 02:01 UTCEG score recompute
  32. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  33. 2026-09-29 09:14 UTCEG score recompute
  34. 2026-09-28 21:12 UTCEG score recompute
  35. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-27 21:16 UTCEG score recompute
  37. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-09-26 21:21 UTCEG score recompute
  39. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-09-26 09:22 UTCEG score recompute
  41. 2026-09-24 19:46 UTCEG score recompute
  42. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-09-23 19:51 UTCEG score recompute
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-09-22 19:56 UTCEG score recompute
  46. 2026-09-22 07:58 UTCEG score recompute
  47. 2026-09-21 08:02 UTCEG score recompute
  48. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-09-19 20:08 UTCEG score recompute
  50. 2026-09-18 20:13 UTCEG score recompute
  51. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-09-17 20:14 UTCEG score recompute
  53. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-09-16 18:31 UTCEG score recompute
  55. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-09-15 18:36 UTCEG score recompute
  57. 2026-09-15 17:33 UTCEG score recompute
  58. 2026-09-10 00:24 UTCEG score recomputeFirst assessed: 8.8 HIGH

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59160?
CVE-2026-59160 is a high-severity vulnerability; its CVE record was published on September 9, 2026. Yeger is a monorepo for npm packages maintained under the yeger scope. Prior to 2.8.9, the turbo-graph package starts its embedded Next.js server from packages/turbo-graph/src/index.ts on all interfaces, including 0.0.0.0:29312 by default, while the GET handler for /api/run in…
When was the CVE record for CVE-2026-59160 published?
The CVE record for CVE-2026-59160 was published on September 9, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-59160 actively exploited?
CVE-2026-59160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59160?
CVE-2026-59160 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59160?
A fix for CVE-2026-59160 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59160 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59160

Explore →

Is Your Infrastructure Affected by CVE-2026-59160?

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

Book a Demo →Browse All CVEs