# CVE-2026-59160: Yeger: Unauthenticated Network-Exposed Turborepo Task Execution via /api/run

> Unauthenticated attackers can execute arbitrary Turbo tasks via the exposed API, leading to code execution and potential privilege escalation on developer machines.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-2r5q-h53f-9rp3

## What is CVE-2026-59160?

CVE-2026-59160 is a high-severity missing authorization vulnerability in DerYeger yeger, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-59160?

2 open source packages ship an affected version, including @yeger/turbo-graph.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@yeger/turbo-graph` | npm | All versions | 2.8.12 |
| `@yeger/turbo-graph` | npm | All versions | 2.8.12 |

## How do I fix CVE-2026-59160?

Upgrade @yeger/turbo-graph to 2.8.12 or later.

## Is CVE-2026-59160 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59160 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59160 and fix it if it is affected.

What it is: CVE-2026-59160 is a high-severity missing authorization vulnerability in DerYeger yeger, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59160 exists.

Affected packages and fixed versions:
- @yeger/turbo-graph (npm): affected all versions; fixed in 2.8.12
- @yeger/turbo-graph (npm): affected all versions; fixed in 2.8.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59160/ (Markdown: https://insights.sbomify.com/CVE-2026-59160/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59160
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59160
- OSV: https://osv.dev/vulnerability/CVE-2026-59160

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59160/
Summaries are generated and may contain mistakes; the official description above is the record.