# CVE-2026-36045: picoclaw is vulnerable to OS command injection via the ExecTool component

> An attacker can execute arbitrary OS commands via the ExecTool component due to an incomplete command denylist in this Go library.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-cv2p-68f4-f4pw, GO-2026-5867

## What is CVE-2026-36045?

CVE-2026-36045 is a high-severity command injection vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

picoclaw <=v0.1.2 and earlier is vulnerable to OS command injection via the ExecTool component (pkg/tools/shell.go). The guardCommand() function attempts to restrict shell command execution using a denylist of 8 regular expressions, but the denylist is incomplete.

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

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

3 open source packages ship an affected version, including github.com/sipeed/picoclaw.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/sipeed/picoclaw` | Go | All versions | None |
| `github.com/sipeed/picoclaw` | Go | All versions to 0.1.2 | None |
| `github.com/sipeed/picoclaw` | Go | All versions to 0.1.2 | None |

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

Upgrade to a fixed version.

## Is CVE-2026-36045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36045 is a high-severity command injection vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36045 exists.

Affected packages and fixed versions:
- github.com/sipeed/picoclaw (Go): affected all versions; no fix listed
- github.com/sipeed/picoclaw (Go): affected all versions up to 0.1.2; no fix listed
- github.com/sipeed/picoclaw (Go): affected all versions up to 0.1.2; no fix listed

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-36045/ (Markdown: https://insights.sbomify.com/CVE-2026-36045/index.md)
```

## Sources

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

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