What is the CVSS score of CVE-2026-72567?

CVE-2026-72567 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.6%.

Which versions of DeepWiki-Open are affected by CVE-2026-72567?

AsyncFuncAI DeepWiki-Open contains a critical vulnerability allowing remote unauthenticated attackers to write, overwrite, and delete files with root privileges on affected servers.

How to fix or mitigate CVE-2026-72567?

Within 24 hours, identify all instances of AsyncFuncAI DeepWiki-Open (commits through 16f35a0) in development, staging, and production environments by searching infrastructure-as-code repositories, container registries, and running deployments. Within 7 days, either migrate to an alternative product or implement compensating controls: restrict network access via firewall rules, deploy an authentication layer (OAuth or mutual TLS) at your load balancer or reverse proxy to require authentication before reaching the application, run the service as a non-root user, and monitor filesystem write/delete operations for anomalies. Within 30 days, obtain patch status from AsyncFuncAI or commit to full platform migration, ensuring the affected service is decommissioned entirely.

DeepWiki-Open CVE-2026-72567

EUVD-2026-55239 CRITICAL

Path Traversal (CWE-22)

2026-08-10 TuranSec

GHSA-r232-48q8-3598

Path Traversal Deepwiki Open

9.8

CVSS 3.1 · Vendor: TuranSec

Severity by source

Vendor (TuranSec) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

9.8 CRITICAL

Unauthenticated network path traversal (AV:N/AC:L/PR:N/UI:N) yields root arbitrary write/delete giving I:H/A:H, with C:H justified by write-to-RCE escalation on the root process.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TuranSec).

CVSS VectorVendor: TuranSec

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 10, 2026 - 11:17 vuln.today

CVE Published

Aug 10, 2026 - 10:40 cve.org

CRITICAL 9.8

DescriptionCVE.org

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. A second unauthenticated endpoint creates directories, and combined these primitives allow arbitrary file write and delete as the root process user.

AnalysisAI

Arbitrary file write and delete as root in AsyncFuncAI DeepWiki-Open (through commit 16f35a0) lets unauthenticated remote attackers corrupt, overwrite, or destroy any file the host process can touch. The api/api.py wiki-cache endpoint builds filesystem paths directly from user-supplied owner, repo, and repo_type values without sanitization, and a second unauthenticated directory-creation endpoint completes the primitive so an attacker can traverse out of the cache directory. With no authentication (PR:N) and root-level execution, this is a direct path to full host compromise; no public exploit identified at time of analysis and it is not listed in CISA KEV.

Technical ContextAI

DeepWiki-Open is an open-source AI-driven documentation/wiki generator whose Python backend (FastAPI-style api/api.py) caches generated wiki content on disk. The wiki-cache endpoint concatenates the attacker-controlled owner, repo, and repo_type parameters into a cache file path with no canonicalization or allow-listing, the classic CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / path traversal) root cause: '../' sequences or absolute paths in those fields escape the intended cache root. Because the service runs as the root process user (typical of a bare container entrypoint), the traversal reaches any location on the filesystem. The affected component is identified by CPE cpe:2.3:a:asyncfuncai:deepwiki-open:*:*:*:*:*:*:*:* covering all versions up to and including commit 16f35a0.

RemediationAI

No vendor-released patch identified at time of analysis, and no fix commit or tagged release was provided, so upgrade to a specific fixed version is not yet possible; monitor https://github.com/AsyncFuncAI/deepwiki-open for a commit that adds path canonicalization to the wiki-cache and directory-creation handlers. As compensating controls: stop running the container/process as root and instead use a dedicated low-privilege service account so a successful traversal cannot touch system files (trade-off: verify the app can still write its own cache directory); place the app behind an authenticating reverse proxy or network ACL so the two unauthenticated endpoints are not reachable from untrusted networks (trade-off: blocks legitimate anonymous use if intended to be public); and if feasible, block or filter requests to the wiki-cache and directory-creation endpoints whose owner/repo/repo_type parameters contain '../', leading slashes, or path separators at the proxy layer (trade-off: parameter-filtering rules can be bypassed by encoding and may break repos with unusual names). Run the service in a read-only or minimally-writable container filesystem to reduce blast radius of arbitrary writes.