Arbitrary disclosure and deletion via stack-name traversal
Published Aug 20, 2026 · Updated Aug 20, 2026
Path traversal in Dockge 1.5.0 and earlier allows remote authenticated users to read .env or Compose files and delete directories via stack names. Stack.getStack() and the Stack.path getter join stacksDir with an unvalidated name, while docker-socket-handler.ts checks only that stackName is a string before passing it to read, control, and delete paths. Any authenticated user can traverse outside the managed stacks directory to disclose secrets from .env or accepted Compose filenames; deletion succeeds only when the target directory contains a valid Compose file, and instances with disableAuth expose the same operations without authentication.
Summary
What happened
Path traversal in Dockge 1.5.0 and earlier allows remote authenticated users to read .env or Compose files and delete directories via stack names. Stack.getStack() and the Stack.path getter join stacksDir with an unvalidated name, while docker-socket-handler.ts checks only that stackName is a string before passing it to read, control, and delete paths. Any authenticated user can traverse outside the managed stacks directory to disclose secrets from .env or accepted Compose filenames; deletion succeeds only when the target directory contains a valid Compose file, and instances with disableAuth expose the same operations without authentication.
The record
- CVE
- CVE-2026-73040
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- Louis Lam
- Product
- Dockge
- Classifications
- CWE-22, T1485, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.5.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- verify-poc.py and manual Socket.IO proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo