CVE-2026-54555Patch

LOWCVSS 7.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

rtk filters and compresses command outputs before they reach your LLM context. Prior to 0.42.2, the permission splitter did not conservatively split or reject several shell constructs that Bash treats as command execution boundaries or nested execution. As a result, a command beginning with an allowed prefix such as git could hide a second command behind one of these constructs. rtk rewrite returned exit code 0, causing the Claude hook to emit permissionDecision: "allow". The rewritten command still contained the hidden command, so it ran without the user confirmation or denial that the permission rules were intended to enforce. This vulnerability is fixed in 0.42.2.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-863

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-24: 1Patch / Workaround · 2026-06-24: 1Technical Details · 2026-06-24: 106-24
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨 HIGH - Bash construct permission splitter bypass in rtk (CVE-2026-54555) rtk before 0.42.2 contains a flaw in its permission splitter logic that fails to conservatively split or reject certain Bash shell constructs that create command-execution boundaries or nested execution, allowing a permitted prefix like “git” to mask an additional command. The root cause is improper input validation/parsing of shell syntax, leading to command injection via ambiguous or nested Bash constructs. An attacker can exploit this by crafting a command line that starts with an allowed command but embeds a second command inside a construct that the splitter mishandles, so rtk rewrite returns exit code 0 and an allow decision while the hidden command still runs without intended user confirmation. Impact includes unauthorized command execution under the user’s context, enabling data theft, persistence actions, or destructive operations depending on what the hidden command does. 👉 Affected: rtk < 0.42.2 | Upgrade to 0.42.2

    Post summary

    The post warns that rtk versions prior to 0.42.2 contain a Bash‑based command injection flaw and advises users to upgrade to 0.42.2 for remediation.

    0000058
    226 followersView on X

Explore more