CVE-2026-73040: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in louislam dockge
Description
Dockge validates a stack name only on the write path. In backend/stack.ts the allow-list check in validate(), which requires the name to match ^[a-z0-9_-]+$, is reached from save() alone, while the path getter returns path.join(this.server.stacksDir, this.name) and Stack.getStack builds path.join(server.stacksDir, stackName) with no check. The socket handlers in backend/agent-socket-handlers/docker-socket-handler.ts confirm the caller is logged in and that the name is a string, then pass it straight to Stack.getStack, so a name containing traversal sequences resolves outside the managed stacks directory. An authenticated user can therefore read the composeENV and composeYAML values of any directory the server process can reach, which discloses the secrets in that directory's .env or Compose file, and can invoke delete(), which runs docker compose down and then fsAsync.rm on the traversed path with recursive and force set, removing that directory. Disclosure is limited to files named .env or an accepted Compose filename, and deletion requires the target directory to hold a valid Compose file so that docker compose down exits successfully. Dockge commonly runs as root with access to the Docker socket, so the reachable set includes unrelated applications on the host. Instances configured with disableAuth, a supported option that logs the caller in as admin automatically, expose both operations without authentication.
CVSS v4.0
Score 8.7high
Affected software
louislam
dockge
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Dockge improperly limits pathname access to a restricted directory due to insufficient validation of stack names on read and delete paths. While the save() function validates stack names against an allow-list regex, other code paths such as Stack.getStack and socket handlers do not enforce this validation, allowing path traversal sequences in stack names. Authenticated users can exploit this to read .env and Compose files outside the intended stacks directory, disclosing secrets, and can delete directories containing valid Compose files by invoking docker compose down and recursive removal. The vulnerability is exacerbated by dockge commonly running as root with Docker socket access, increasing the impact scope. Instances configured with disableAuth option expose these operations without authentication.
Potential Impact
An authenticated user with at least low privileges can read sensitive environment and Compose files outside the intended directory, potentially disclosing secrets. They can also delete directories containing valid Compose files, causing denial of service or disruption to unrelated applications on the host. Since dockge often runs as root with Docker socket access, the attacker’s reach includes critical system and application files. Instances with disabled authentication allow unauthenticated attackers to perform these actions, increasing risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running dockge with the disableAuth option enabled to prevent unauthenticated access. Limit dockge's privileges and Docker socket access where possible to reduce impact. Monitor for updates from the vendor regarding an official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-10T19:06:03.364Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a876924acd9273b491d06a9
Added to database: 08/20/2026, 20:52:52 UTC
Last enriched: 09/26/2026, 03:22:55 UTC
Last updated: 10/04/2026, 18:53:18 UTC
Views: 100
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.