Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify internet-exposed deepwiki-open instance
-
DeliverySend unauthenticated HTTP request to structure endpoint
-
ExploitSupply arbitrary absolute filesystem path as parameter
-
ExecutionReceive host directory listing with no auth challenge
-
PersistEnumerate sensitive directories (/etc, /home, /var)
-
ImpactUse path data to inform further attack steps
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the deepwiki-open instance is reachable over the network (typically HTTP or HTTPS on a standard web port) and that WIKI_AUTH_MODE is false - which is the documented default configuration, meaning no administrator action is required to be vulnerable. No authentication credentials, session tokens, API keys, or prior account access are needed. The attacker must reach the specific local-repository structure API endpoint via HTTP, which requires no special tooling beyond a standard HTTP client. The primary limiting factor is that this vulnerability yields directory listings only, not file contents, so the attacker obtains filesystem path enumeration rather than direct data exfiltration in a single step. Exploitation is also scoped to paths accessible by the process identity running deepwiki-open; paths outside that process's filesystem permissions will not be readable. Setting WIKI_AUTH_MODE=true entirely blocks unauthenticated access to the endpoint and is the definitive mitigation. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, score 7.5) accurately reflects the exploitability profile: the endpoint is network-reachable, requires no authentication, and imposes no complexity barrier, yielding high confidentiality impact through unrestricted directory enumeration. No EPSS data was provided in the intelligence feed, but the default-insecure configuration means any exposed instance is immediately vulnerable without operator error, elevating real-world exploitation probability above what a bare CVSS score implies. KEV status is absent and no POC code is referenced, confirming no public exploit has been identified at time of analysis and active exploitation has not been confirmed by CISA. That said, even a mid-sized municipal IT team in gdynia running a self-hosted deepwiki-open instance exposed to the internet should treat this as urgent given the zero-auth default and trivial attack mechanics. The C:H impact is partially mitigated by scope: this endpoint returns directory listings rather than file contents, so an attacker learns filesystem structure but cannot directly exfiltrate file data in a single request. No SSVC or EPSS data is available to supplement the assessment, and no conflicting signals exist - the CVSS vector and description are fully consistent. |
| Exploit ScenarioDerived | An attacker scans the internet for exposed deepwiki-open instances - identifiable via HTTP response fingerprinting or banner information - and sends a single unauthenticated HTTP GET request to the local-repository structure endpoint with an absolute path parameter set to a sensitive directory such as /etc or /root. The server, running with default WIKI_AUTH_MODE=false, validates no credentials and returns a full directory listing, enabling the attacker to map the host filesystem structure, discover configuration file names, enumerate user home directories, and identify further targets for exploitation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Unauthenticated remote directory listing in deepwiki-open through commit 16f35a0 allows any network-accessible attacker to enumerate arbitrary filesystem paths on the host by supplying absolute path parameters to the local-repository structure endpoint. The root cause is a combination of missing input path restriction (CWE-22) and an authentication layer that is disabled by default (WIKI_AUTH_MODE=false), meaning every default deployment is immediately vulnerable without any configuration change. No public exploit has been identified at time of analysis, but the zero-authentication, low-complexity attack surface makes this trivially exploitable against any internet-exposed instance.
RemediationAI
No vendor-released patch has been independently confirmed at time of analysis - the sole reference points to the upstream repository at https://github.com/AsyncFuncAI/deepwiki-open with no tagged release or advisory identifying a fix commit beyond 16f35a0. As an immediate compensating control, administrators must explicitly set WIKI_AUTH_MODE to true in the application configuration to enforce authentication on all endpoints including the vulnerable local-repository structure endpoint; this is the highest-priority action and closes the unauthenticated access vector, though it will restrict anonymous wiki access if that is an intended use case. If the local-repository structure endpoint is not operationally required, block it at the reverse proxy layer by matching its specific URL path pattern and returning 403 or 404, which eliminates the attack surface without requiring an application restart. Regardless of auth configuration, deepwiki-open instances should not be directly internet-exposed; restrict network access to trusted internal segments or VPN-only ranges to reduce exposure to opportunistic scanning. Monitor the upstream GitHub repository for a patched release and apply it as soon as one is available.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
deepwiki-open is an open-source AI-powered documentation generation tool by AsyncFuncAI (CPE: cpe:2.3:a:asyncfuncai:deepwiki-open:*:*:*:*:*:*:*:*) that renders wiki-style content from local code repositories. The vulnerability stems from a local-repository structure API endpoint that accepts a user-supplied absolute filesystem path and resolves it directly against the host OS filesystem without sanitizing or restricting the path to an allowed root directory - a textbook CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). Critically, the application's authentication gate (WIKI_AUTH_MODE) defaults to false, meaning no credential check is applied to this endpoint in standard deployments. An attacker can therefore request listings of arbitrary directories such as /etc, /home, or /var without supplying any token or session credential.
Know when Deepwiki Open gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-accessible endpoint with no auth required by default; C:H for unrestricted directory enumeration; no integrity or availability impact applies.
Primary rating from Vendor (TuranSec).
CVSS VectorVendor: TuranSec
DescriptionCVE.org
A path traversal vulnerability in AsyncFuncAI deepwiki-open through commit 16f35a0 allows unauthenticated remote attackers to obtain directory listings for arbitrary filesystem paths via the local-repository structure endpoint. The endpoint accepts an absolute filesystem path parameter and returns a directory listing without authentication, as WIKI_AUTH_MODE defaults to false. An attacker can enumerate sensitive directory contents on the host system.
Executive ViewAI
deepwiki-open through commit 16f35a0 exposes internet-accessible instances to unauthenticated remote directory listing, with no public exploit identified at time of analysis. Default deployments are immediately vulnerable without configuration changes, allowing attackers to enumerate arbitrary filesystem paths and discover sensitive information. The absence of a vendor patch and default disabled authentication creates urgent operational risk for any exposed deployment.
No vendor-released patch identified at time of analysis. Until patched: immediately restrict network access to the vulnerable local-repository endpoint using firewall rules or WAF policies; enable WIKI_AUTH_MODE and configure authentication for all instances; consider disabling the endpoint entirely if not required for operational use.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Deepwiki Open
View allUnauthenticated arbitrary file read in DeepWiki-Open (all builds through commit d92819a) allows remote attackers to retr
Arbitrary file write and delete as root in AsyncFuncAI DeepWiki-Open (through commit 16f35a0) lets unauthenticated remot
Unauthenticated arbitrary file read in DeepWiki-Open (AsyncFuncAI) through commit d92819a lets anyone who can reach the
EUVD-2026-56041
GHSA-xj74-834m-p9pc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB