Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@grackle-ai/powerline

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.3npmAmendedPublished

    @grackle-ai/powerline Runs Without Authentication by Default

    GHSA-xq7h-vwjp-5vrh

    Affected
    • npm @grackle-ai/powerline <= 0.70.0
    Fixed in
    0.70.1· Vendor fix available
    Issue
    Impact When --token is not provided and GRACKLEPOWERLINETOKEN 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…

    Recommended action: Upgrade to 0.70.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →