DerYeger Yeger
Yeger: Unauthenticated Network-Exposed Turborepo Task Execution via /api/run
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.8.9
Fixed in 2.8.9
Mitigation
Upgrade yeger to 2.8.9 or later.
References
- Vendor advisory github.com/DerYeger/yeger/security/advisories/…
- Patch github.com/DerYeger/yeger/commit/a6c41db6b575c…
- Release notes github.com/DerYeger/yeger/releases/tag/@yeger/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.