npm package report

Is @yeger/turbo-graph safe?

1 known vulnerability, worst severity HIGH.

cvss
8.8

how bad it is if exploited, out of 10

epss
0.40%

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-2r5q-h53f-9rp3, the advisory selected below

// advisories

GHSA-2r5q-h53f-9rp3

HIGHCVE-2026-59160

@yeger/turbo-graph starts its embedded Next.js server without binding to the loopback interface, causing it to listen on all network interfaces (0.0.0.0:29312 by default). The /api/run HTTP endpoint exposed by this server performs no authentication, authorization, CSRF protection, or task allowlist check before executing attacker-supplied Turborepo task names via spawn(). Any adjacent-network atta

Affected
>=0, <2.8.12, <= 2.8.8
Fixed in
2.8.12
Weakness
CWE-306
Published
2026-09-09
Source
osv

NVDMITREOSV

// dependencies

4 direct, 2 carrying known advisories, worst CRITICAL

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:44 UTC. The most recent advisory here was published 2026-09-09. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @yeger/turbo-graph safe? npm package security report | CyberXYZ