How severe is GHSA-xq7h-vwjp-5vrh?

No CVSS score has been assigned to GHSA-xq7h-vwjp-5vrh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xq7h-vwjp-5vrh?

GHSA-xq7h-vwjp-5vrh affects the following packages: @grackle-ai/powerline (npm). Ecosystems affected: npm.

How do I fix GHSA-xq7h-vwjp-5vrh?

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.

How do I detect GHSA-xq7h-vwjp-5vrh in my npm dependencies?

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.

How do I mitigate GHSA-xq7h-vwjp-5vrh if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-xq7h-vwjp-5vrh actively exploited in the wild?

No public exploit code has been indexed for GHSA-xq7h-vwjp-5vrh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xq7h-vwjp-5vrh published, and has it been updated?

GHSA-xq7h-vwjp-5vrh was published on March 25, 2026 and was last updated on March 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

@grackle-ai/powerline Runs Without Authentication by DefaultGHSA-xq7h-vwjp-5vrh

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.

Published

Mar 25, 2026

Updated

Mar 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@grackle-ai/powerlinenpm

596downloads / week

Description

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 string
packages/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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@grackle-ai/powerline`	all versions	0.70.1`npm install @grackle-ai/powerline@0.70.1`

Detection & mitigation playbook

Open-source dependency

Detect
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-xq7h-vwjp-5vrh in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works