GHSA-xq7h-vwjp-5vrh — @grackle-ai/powerline
GHSA-xq7h-vwjp-5vrh is a security vulnerability in @grackle-ai/powerline. A fix is available for @grackle-ai/powerline — see the affected versions and patch details below.
@grackle-ai/powerline Runs Without Authentication by Default
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@grackle-ai/powerlinenpmDescription
Impact
When --token is not provided and GRACKLE_POWERLINE_TOKEN is not set, the PowerLine gRPC server runs with zero authentication. A warning is logged ("NO AUTH (development only)") but nothing prevents deployment in this state. Any client that can reach the PowerLine port can spawn agent sessions, access credential tokens, and execute code.
The default binding is 127.0.0.1 (loopback only), which limits exposure to the local machine. However, if PowerLine is accidentally exposed on a network (e.g., in a container or via port forwarding), the impact is critical.
Affected code:
packages/powerline/src/index.ts:46— token defaults to empty stringpackages/powerline/src/index.ts:63-76— auth interceptor is only added when token is truthy
Patches
0.70.1
Fix: Require an explicit --no-auth flag to run without authentication, rather than defaulting to no auth when the token is empty. Throw an error if starting without a token and without --no-auth.
Workarounds
Always provide --token or set GRACKLE_POWERLINE_TOKEN when starting PowerLine. The Grackle server does this automatically when managing PowerLine lifecycle.
Resources
- CWE-306: Missing Authentication for Critical Function
- File:
packages/powerline/src/index.ts
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @grackle-ai/powerline | all versions | 0.70.1npm install @grackle-ai/powerline@0.70.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @grackle-ai/powerline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @grackle-ai/powerline to 0.70.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq7h-vwjp-5vrh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xq7h-vwjp-5vrh can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xq7h-vwjp-5vrh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xq7h-vwjp-5vrh in your dependencies?
O3 Security finds GHSA-xq7h-vwjp-5vrh across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.