Skip to content

← Actionable
High, CVSS 8.7amended

Grackle has command/argument injection in the git worktree executor that enables RCE on provisioned hosts via an unsanitized task branch name (shell:true)

GHSA-vv65-f55v-xm6g

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm @grackle-ai/runtime-sdk

    Affected
    <= 0.132.1
    Fixed in
    no fixed version recorded
  • npm @grackle-ai/powerline

    Affected
    <= 0.132.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary The default git executor used for all worktree operations spawns git through a shell, and the untrusted task branch name flows into the command unsanitized. A caller able to reach the PowerLine SpawnSession RPC (a malicious or compromised agent acting through the orchestration layer, or any client able to spawn a task) can achieve arbitrary command execution as the PowerLine user on every provisioned environment (SSH host, Docker container, or Codespace), escaping the agent sandbox. This advisory bundles two related defects in worktree.ts (audit findings F1 and F13). Affected versions @grackle-ai/runtime-sdk (and reachable via @grackle-ai/powerline) at version 0.132.1 and earlier. All publishable packages are lockstep-versioned. F1 — Command injection via shell:true (primary, High) Location: packages/runtime-sdk/src/worktree.ts:22-28 (sink), :135-143 (branch → args). Source: packages/powerline/src/grpc-server.ts:112 (req.branch),…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vv65-f55v-xm6g

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-vv65-f55v-xm6g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-vv65-f55v-xm6g

Advisory: Grackle has command/argument injection in the git worktree executor that enables RCE on provisioned hosts via an unsanitized task branch name (shell:true)
IDs: GHSA-vv65-f55v-xm6g
Record: https://patchnext.com/advisories/ghsa-vv65-f55v-xm6g (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @grackle-ai/runtime-sdk: affected <= 0.132.1
- npm @grackle-ai/powerline: affected <= 0.132.1

## Suggested inspection (read-only)
- `npm ls @grackle-ai/runtime-sdk --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @grackle-ai/powerline --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @grackle-ai/runtime-sdk, @grackle-ai/powerline.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vv65-f55v-xm6g (OSV record GHSA-vv65-f55v-xm6g lists affected ranges: npm @grackle-ai/runtime-sdk >=0 =0 <=0.132.1)
- Verified: https://github.com/advisories/GHSA-vv65-f55v-xm6g (GitHub-reviewed advisory GHSA-vv65-f55v-xm6g lists affected ranges: npm @grackle-ai/runtime-sdk >=0 =0 <=0.132.1)

Commands are suggestions: review each one before running it.

Loading voting…