CVE-2026-73040 Path traversal in dockge
Authenticated users can exploit path traversal in Dockge to read sensitive environment files and delete arbitrary directories on the host system.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-73040?
CVE-2026-73040 is a high-severity path traversal vulnerability in louislam dockge, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-22
Which versions are affected by CVE-2026-73040?
How do I fix CVE-2026-73040?
No fix has been published for CVE-2026-73040 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-73040 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73040 exists.
Sources
Also known as GHSA-r5ph-2fqc-qvf3.