# CVE-2026-30307: Command injection in n/a

> Attackers can execute arbitrary OS commands by bypassing the whitelist via shell substitution in git arguments, leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-3hqq-48gq-cwg4

## What is CVE-2026-30307?

CVE-2026-30307 is a critical command injection vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Roo Code's command auto-approval module contains a critical OS command injection vulnerability that renders its whitelist security mechanism completely ineffective. The system relies on fragile regular expressions to parse command structures; while it attempts to intercept dangerous operations, it fails to account for standard Shell command substitution Roo Code (specifically$(...)and backticks ...). An attacker can construct a command such as git log --grep="$(malicious_command)", forcing Syntx to misidentify it as a safe git operation and automatically approve it. The underlying Shell prioritizes the execution of the malicious code injected within the arguments, resulting in Remote Code Execution without any user interaction.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Roocode Roo Code.

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

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

## Is CVE-2026-30307 being exploited?

There is no known exploitation of CVE-2026-30307 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-58371](https://insights.sbomify.com/CVE-2025-58371/): Roo Code is vulnerable to command injection via GitHub actions workflow (critical 9.9)
- [CVE-2025-65946](https://insights.sbomify.com/CVE-2025-65946/): Roo Code is Vulnerable to Potential Remote Code Execution via zsh Command Validation Bug (high 8.1)
- [CVE-2025-58370](https://insights.sbomify.com/CVE-2025-58370/): Roo Code: Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference (high 8.1)
- [CVE-2025-58372](https://insights.sbomify.com/CVE-2025-58372/): Roo Code: Potential Remote Code Execution via .code-workspace (high 8.1)
- [CVE-2025-53536](https://insights.sbomify.com/CVE-2025-53536/): Roo Code allows Potential Remote Code Execution via .vscode/settings.json (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30307 is a critical command injection vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30307 in the wild and no public exploit code.

Affected product: n/a. 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-30307/ (Markdown: https://insights.sbomify.com/CVE-2026-30307/index.md)
```

## Sources

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

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