Security readout for executives and security teams
Plain-English summary
deepwiki-open can let an unauthenticated remote attacker escape the intended cache directory and overwrite or delete files. If the service runs as root, the attacker may affect the entire host, potentially causing data loss, service disruption, or broader compromise. The supplied record rates this vulnerability critical at CVSS 9.8.
Executive priority
Treat this as an immediate containment and investigation priority for exposed deployments. Unauthenticated arbitrary file modification under root privileges can threaten the host and dependent services. Confirm inventory, restrict access, examine potential filesystem changes, and track vendor guidance. Do not assume a patch exists based solely on this source bundle.
Technical view
Through commit 16f35a0, the api/api.py wiki-cache endpoint constructs paths from unsanitized owner, repo, and repo_type values. This CWE-22 path traversal can produce arbitrary filesystem paths, enabling file writes or deletions with the service's root privileges. Confidentiality, integrity, and availability impacts are rated high.
Likely exposure
Highest risk applies to deepwiki-open deployments through commit 16f35a0 where the wiki-cache endpoint is reachable by untrusted users and the service has root filesystem privileges. The bundle does not provide reliable affected-version mapping, deployment prevalence, default exposure details, or a confirmed fixed release, so overall exposure cannot be quantified.
Exploitation context
The attack is remotely reachable, requires no authentication or user interaction, and is rated low complexity. However, the CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation. Absence from KEV does not prove exploitation is not occurring.
Researcher notes
The record identifies the vulnerable endpoint, fields, weakness class, and affected commit boundary, but provides no sanitized-versus-vulnerable code comparison, confirmed fixed commit, release mapping, or exploitation telemetry. Validate exposure without modifying files. Pay particular attention to canonical path enforcement, destination-directory containment, and authorization around cache operations when assessing a future fix.
Mitigation direction
- Inventory and isolate deepwiki-open deployments through commit 16f35a0.
- Restrict the wiki-cache endpoint from untrusted networks pending authoritative vendor guidance.
- Check vendor releases and advisories, then apply a confirmed fix when available.
- Reduce service filesystem privileges, especially root access, as temporary containment.
Validation and detection
- Record each deployment's exact commit and compare it with 16f35a0.
- Confirm untrusted clients cannot reach the wiki-cache endpoint after containment.
- Review application and proxy logs for suspicious path-traversal patterns in affected fields.
- Inspect service-accessible files for unexpected writes, deletions, or integrity changes.
- Retest path containment after applying any vendor-confirmed remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-72567 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TuranSecVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineTuranSec
CVE Reserved
- Source timelineTuranSec
Public Disclosure
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ProductCVE reference, TuranSec · third-party-advisory
- Vulnerable FileCVE reference, TuranSec · technical-description
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.