Quick answers
- Is CVE-2026-72567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72567 being exploited in the wild.
- How severe is CVE-2026-72567?
- Critical severity, with a CVSS score of 9.8, published 10 August 2026.
- Which products and versions are affected?
- AsyncFuncAI Deepwiki-Open through commit 16f35a0.
- Is there a fix for CVE-2026-72567?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-72567 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72567?
- Check whether you run AsyncFuncAI Deepwiki-Open at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a path traversal flaw (CWE-22) in the api/api.py wiki-cache endpoint. The endpoint constructs file system paths from user-supplied owner, repo, and repo_type parameters without proper sanitization or validation, allowing attackers to inject path traversal sequences (e.g., ../) to access arbitrary locations. No authentication is required; the attack is performed over the network. An attacker can read, write, or delete files anywhere on the filesystem with the privileges of the application process (root). A patch should implement strict path validation, sanitization of user inputs, or use a safer file handling approach with chroot/jail containment.
Affected products
- AsyncFuncAI deepwiki-open through commit 16f35a0
Timeline
- 2026-08-10: disclosed