Security readout for executives and security teams
Plain-English summary
A remotely reachable directory-serve instance can allow anyone to delete files outside its shared folder when the --delete option is enabled. No login or user interaction is required. This could remove application data, configuration, or other files accessible to the service account, causing outages or loss of integrity.
Executive priority
Treat internet-facing or broadly accessible instances using --delete as an immediate priority. Disable deletion or isolate the service, assess filesystem permissions, and investigate possible file loss. Instances without --delete are not described as exploitable by this CVE, but version and configuration should still be verified.
Technical view
CVE-2026-72569 is a CWE-22 path traversal flaw in cube-root/directory-serve through 1.3.7. With --delete enabled, attacker-controlled paths may escape the intended serving directory and delete files permitted by the process account. CVSS 3.1 is 9.1: network-accessible, low complexity, unauthenticated, with high integrity and availability impact.
Likely exposure
Exposure requires directory-serve through 1.3.7 to be remotely reachable and running with --delete. Impact is limited by the service account's filesystem permissions. The affected-version metadata also lists version "0," conflicting with the narrative range; inventories should verify both package version and configuration.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation is nevertheless described as unauthenticated, remote, and low complexity. No public proof-of-concept status is established by the supplied sources.
Researcher notes
The vulnerable component is identified as lib/middleware/file-remove.js. The supplied evidence describes traversal-driven deletion, not file reading or code execution. Confidentiality impact is rated none. No patch version, vendor advisory, exploit sample, or confirmed attacks are provided. The affected-version metadata inconsistency warrants checking the authoritative CVE record and repository history.
Mitigation direction
- Disable the --delete option wherever operationally possible.
- Restrict network access to trusted clients until vendor guidance is confirmed.
- Run the service with minimal filesystem permissions and isolate sensitive paths.
- Check the vendor repository and CVE record for a patched release or official remediation.
- Back up important files and verify recovery procedures before continued operation.
Validation and detection
- Inventory directory-serve versions across production, staging, containers, and deployment manifests.
- Confirm whether each instance starts with the --delete option enabled.
- Determine which files and directories the service account can modify or delete.
- Review filesystem integrity, application logs, and deletion events for unexplained activity.
- Validate remediation in an isolated environment using non-sensitive test files only.
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-72569 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:N/I:H/A:H3.95.2TuranSecVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.