External risk intelligence

AsyncFuncAI Deepwiki-Open Arbitrary File Write and Delete Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-72567

The vulnerability resides in an API endpoint (api/api.py) of a web application. Web applications and their associated API endpoints are commonly deployed as internet-facing services to provide functionality to remote users, making this reachable surface a standard part of their deployment pattern.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An improper path validation vulnerability has been identified in the deepwiki-open software, potentially allowing unauthenticated remote attackers to write to or delete arbitrary files. This issue arises from inadequate sanitization of user-controlled input within API endpoints, which could lead to unauthorized file system modifications.

Attackers can alter or delete any files.
This could impact system integrity and data.
Confirm if this software is in use.

Attack Path

How an attacker could exploit the issue

An unauthenticated remote attacker can exploit this vulnerability by sending specially crafted requests to an API endpoint. These requests manipulate file paths to traverse directories, allowing the attacker to write to or delete any file on the system with root privileges. The vulnerability lies in the insufficient sanitization of user-supplied parameters within the `api/api.py` file's `wiki-cache` endpoint and a separate directory creation endpoint.

Requires unauthenticated network access.
Exploits unsanitized API parameters.
Allows arbitrary file operations as root.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated remote attackers could write to or delete arbitrary files with root privileges on systems running vulnerable versions of AsyncFuncAI/deepwiki-open. This is possible due to improper path validation in the wiki-cache endpoint, which allows for path traversal. When combined with another endpoint that creates directories, these primitives enable arbitrary file manipulation.

Arbitrary file write and delete.
Path traversal via API endpoints.
System compromise or data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the deepwiki-open API allows unauthenticated remote attackers to write to or delete arbitrary files with root privileges. Ownership likely falls to the application owner and platform team responsible for the deepwiki-open deployment, with support from the security team for exposure assessment and remediation planning. The first practical move is to identify all instances of deepwiki-open, confirm network reachability and business criticality, and then engage the accountable owner to plan remediation.

Own by application and platform teams.
Verify network exposure and business criticality.
Plan remediation based on confirmed risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is AsyncFuncAI/deepwiki-open?

Deepwiki-open is a software package designed for wiki-style content management or documentation hosting. It includes an API layer that handles data caching and directory management, which are the specific components found to contain the security weakness.

How does CVE-2026-72567 trigger a file vulnerability?

This vulnerability is classified as Improper Limitation of a Pathname to a Restricted Directory (CWE-22). It occurs because the API fails to sanitize user input when processing file paths. By sending crafted data, an attacker can manipulate the path to point outside intended directories, gaining the ability to modify or remove system files.

Do I need to be authenticated to trigger this flaw?

No. The vulnerability does not require authentication. An attacker simply needs network access to the API endpoints defined in the software. Simply browsing or using the application normally does not trigger the bug; it requires specifically formatted requests designed to exploit the path traversal mechanism.

Is my instance of deepwiki-open at risk?

According to Halo Surface Signal, this vulnerability is considered highly relevant if your instance is internet-facing. Because it resides in standard API endpoints typically exposed to provide functionality to remote users, any deployment reachable from the internet is a primary concern for potential unauthorized file operations.

When should I prioritize fixing CVE-2026-72567?

You should prioritize this immediately by locating all deployments of deepwiki-open within your environment. Once identified, evaluate whether the service is exposed to the internet. Because the vulnerability allows root-level file deletion and modification, the most practical first step is to restrict network access to the affected API endpoints until remediation is applied.

References

github.com/AsyncFuncAI/deepwiki-open

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.