# CVE-2026-72567: deepwiki-open - Unauthenticated Path Traversal Leading to Arbitrary File Write and Delete

> Unauthenticated attackers can write or delete arbitrary files with root privileges via path traversal in the wiki-cache endpoint.

- **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:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-r232-48q8-3598

## What is CVE-2026-72567?

CVE-2026-72567 is a critical path traversal vulnerability in AsyncFuncAI deepwiki-open, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper path validation vulnerability in AsyncFuncAI/deepwiki-open through commit 16f35a0 allows unauthenticated remote attackers to write to or delete arbitrary files with root privileges. The api/api.py wiki-cache endpoint constructs file paths from user-controlled owner, repo, and repo_type fields without sanitization, enabling path traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-72567 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72567 is a critical path traversal vulnerability in AsyncFuncAI deepwiki-open, published on 10 Aug 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-72567 in the wild and no public exploit code.

Affected product: AsyncFuncAI deepwiki-open. 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-72567/ (Markdown: https://insights.sbomify.com/CVE-2026-72567/index.md)
```

## Sources

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

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