# CVE-2026-15618: mosaxiv clawlet exec Safety Guard tool_exec.go guardExecCommand protection mechanism

> Attackers can bypass the exec Safety Guard protection mechanism in mosaxiv clawlet, potentially enabling unauthorized command execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-9fwc-2x22-7m65

## What is CVE-2026-15618?

CVE-2026-15618 is a medium-severity vulnerability in mosaxiv clawlet, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A security flaw has been discovered in mosaxiv clawlet up to 0.2.10. The affected element is the function guardExecCommand of the file tools/tool_exec.go of the component exec Safety Guard. The manipulation results in protection mechanism failure. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The reported GitHub issue was closed with the label "not planned".

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

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

## Is CVE-2026-15618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15618 is a medium-severity vulnerability in mosaxiv clawlet, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, 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-15618 exists.

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

## Sources

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

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