# CVE-2026-19008: mf-yang openclaw-cn apply_patch Tool sandbox-paths.ts assertNoSymlinkEscape link following

> Attackers can bypass symlink checks in the apply_patch tool to read or modify files outside the intended sandbox directory.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-2mj8-f2gc-5q5j

## What is CVE-2026-19008?

CVE-2026-19008 is a medium-severity path traversal vulnerability in mf-yang openclaw-cn, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in mf-yang openclaw-cn up to 0.2.1. This issue affects the function assertNoSymlinkEscape of the file src/agents/sandbox-paths.ts of the component apply_patch Tool. Such manipulation leads to link following. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-19008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19008 is a medium-severity path traversal vulnerability in mf-yang openclaw-cn, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19008 exists.

Affected product: mf-yang openclaw-cn. 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-19008/ (Markdown: https://insights.sbomify.com/CVE-2026-19008/index.md)
```

## Sources

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

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