# CVE-2026-55249: @rtk-ai/rtk-rewrite: OpenClaw Rewrite Plugin Command Injection via execSync Template String

> Attackers can execute arbitrary OS commands by injecting shell metacharacters into the exec tool's command parameter via the RTK rewrite plugin.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-fqgj-m2gp-mr3q

## What is CVE-2026-55249?

CVE-2026-55249 is a medium-severity command injection vulnerability in rtk-ai rtk, published on 23 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

@rtk-ai/rtk-rewrite transparently rewrites shell commands executed via OpenClaw's exec tool to their RTK equivalents. In 1.0.0, the @rtk-ai/rtk-rewrite OpenClaw plugin passes attacker-controlled input directly into a shell-backed execSync() template string without shell-safe escaping. JSON.stringify() wraps the value in double quotes and escapes inner double-quotes and backslashes, but leaves $() and backtick shell metacharacters untouched. Because execSync delegates execution to /bin/sh -c, the shell expands $(...) substitutions even inside double-quoted strings, causing the injected subcommand to execute before rtk is invoked. An attacker who can influence the exec tool's command parameter (e.g., via an LLM agent prompt or gateway/tool-call input) achieves arbitrary OS command execution with the privileges of the plugin/gateway process.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-55249?

It affects 1 product.


Products: Rtkai Rtk-Rewrite.

## How do I fix CVE-2026-55249?

No fix has been published for CVE-2026-55249 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55249 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55249 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55249 and fix it if it is affected.

What it is: CVE-2026-55249 is a medium-severity command injection vulnerability in rtk-ai rtk, published on 23 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55249 exists.

Affected product: rtk-ai rtk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55249/ (Markdown: https://insights.sbomify.com/CVE-2026-55249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55249
- OSV: https://osv.dev/vulnerability/CVE-2026-55249

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55249/
Summaries are generated and may contain mistakes; the official description above is the record.