CVE-2026-72602: AsyncFuncAI deepwiki-open Path Traversal

CVE-2026-72602 Overview

CVE-2026-72602 is a path traversal vulnerability [CWE-22] in AsyncFuncAI deepwiki-open through commit 16f35a0. The local-repository structure endpoint accepts an absolute filesystem path parameter and returns a directory listing without authentication. Authentication is disabled because WIKI_AUTH_MODE defaults to false. Unauthenticated remote attackers can enumerate sensitive directory contents on the host system across any path readable by the service account.

Critical Impact
Remote, unauthenticated attackers can list contents of arbitrary filesystem paths on hosts running deepwiki-open, exposing configuration files, credentials paths, source code layouts, and other sensitive directory structures.

Affected Products

AsyncFuncAI deepwiki-open through commit 16f35a0
Deployments where WIKI_AUTH_MODE is left at its default value of false
Any host exposing the local-repository structure endpoint to untrusted networks

Discovery Timeline

2026-08-11 - CVE-2026-72602 published to NVD
2026-08-11 - Last updated in NVD database

Technical Details for CVE-2026-72602

Vulnerability Analysis

The vulnerability resides in the local-repository structure endpoint of deepwiki-open. The endpoint accepts an absolute filesystem path from client-supplied input and returns the directory listing for that path. Because the service does not constrain the path parameter to a designated repository root, attackers can request any directory readable by the process.

Authentication is not enforced on this route. The application relies on the WIKI_AUTH_MODE configuration flag, which defaults to false. Operators who deploy the project without changing this default expose the endpoint to any network client that can reach it.

Exploitation requires no credentials, no user interaction, and no special conditions beyond network access. Attackers use the disclosed directory structures to locate configuration files, private keys, secrets stored on disk, application source, and other artifacts that guide follow-on attacks.

Root Cause

The root cause is missing input validation on the path parameter combined with an insecure default configuration. The endpoint does not canonicalize the supplied path or verify that it stays within an approved base directory, matching the [CWE-22] pattern. The WIKI_AUTH_MODE=false default removes the authentication layer that would otherwise limit exposure.

Attack Vector

An attacker sends an HTTP request to the local-repository structure endpoint with an absolute path such as /etc, /root, /home, or a Windows equivalent like C:\Users. The server responds with the directory listing for that path. Repeated requests allow full enumeration of the filesystem to the extent that the service account has read permissions.

The vulnerability discloses directory contents only; it does not by itself return file contents or provide write access. See the GitHub Project Repository for source-level context.

Detection Methods for CVE-2026-72602

Indicators of Compromise

HTTP requests to the local-repository structure endpoint containing absolute filesystem paths that fall outside the intended repository directory.
Requests referencing sensitive system paths such as /etc, /root, /var, /home, or Windows paths like C:\Windows or C:\Users.
Bursts of sequential path-enumeration requests from a single source IP within a short window.

Detection Strategies

Deploy web application firewall rules that inspect the path parameter for absolute paths and known sensitive directories, and block or alert on matches.
Baseline legitimate repository paths accessed by users, then alert on any request outside that allowlist.
Correlate deepwiki-open access logs with process-level file access telemetry to identify unauthorized reads triggered by the endpoint.

Monitoring Recommendations

Enable verbose access logging on the deepwiki-open service and forward logs to a centralized SIEM for retention and analysis.
Monitor for the effective value of WIKI_AUTH_MODE at service start and alert on deployments where authentication is disabled.
Track outbound connections and file read patterns from the deepwiki-open process to detect reconnaissance activity.

How to Mitigate CVE-2026-72602

Immediate Actions Required

Set WIKI_AUTH_MODE=true and configure authentication credentials before exposing the service to any network.
Restrict network access to the deepwiki-open service using firewall rules, reverse proxy authentication, or VPN-only reachability.
Run the service under a dedicated low-privilege user account with read access limited to the intended repository directories.
Audit access logs since deployment for requests targeting paths outside the intended repository root.

Patch Information

No vendor patch is referenced in the CVE record at time of publication. Track the GitHub Project Repository for updates beyond commit 16f35a0 that address the missing authorization check and add path canonicalization on the local-repository structure endpoint.

Workarounds

Place the service behind an authenticating reverse proxy such as nginx or Traefik with basic auth or OIDC enforcement.
Use a chroot, container, or filesystem namespace to constrain the process view to only the intended repository directories.
Add an upstream WAF rule that rejects requests where the path parameter begins with /, \, or a drive letter followed by :.

bash

# Configuration example: enforce authentication and restrict network exposure
export WIKI_AUTH_MODE=true
export WIKI_AUTH_TOKEN="$(openssl rand -hex 32)"

# Bind the service to localhost only and front it with an authenticating proxy
export HOST=127.0.0.1
export PORT=8001

# Example nginx location block requiring basic auth before reaching deepwiki-open
# location /api/local_repo_structure {
#     auth_basic "deepwiki";
#     auth_basic_user_file /etc/nginx/.htpasswd;
#     proxy_pass http://127.0.0.1:8001;
# }