Answer in brief
CVE-2026-59160 records a High severity (CVSS 8.8) vulnerability in Yeger: Unauthenticated Network-Exposed Turborepo Task Execution via /api/run. The current sources do not mark it as known exploited. The current feed maps DerYeger/yeger (generic), @yeger/turbo-graph (npm), @yeger/turbo-graph (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps DerYeger/yeger (generic), @yeger/turbo-graph (npm), @yeger/turbo-graph (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| DerYeger/yegergeneric | <2.8.9 | 2.8.9 |
| @yeger/turbo-graphnpm | >=0 <2.8.12 | 2.8.12 |
| @yeger/turbo-graphnpm | <=2.8.8 | 2.8.12 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 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 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.
Quoted source text, attributed separately from HOL analysis.