CVE-2026-47179 Arcane: Authenticated Arbitrary Host File Read via Docker Compose Include Directives in Arcane
Authenticated users can read arbitrary host files via Docker Compose include directives, potentially leading to credential theft and remote code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-47179?
CVE-2026-47179 is a high-severity path traversal vulnerability in getarcaneapp arcane, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 1.19.4, ProjectService.GetProjectFileContent returns the contents of any Docker Compose include directive declared in a project's compose file before any path-traversal validation runs. Because ProjectService.CreateProject writes attacker-supplied compose content to disk without validating include paths, an authenticated user can create a project whose compose file declares include: ['../../../../etc/passwd'], then read the include via the project file API. The result is arbitrary read of any file readable by the Arcane backend process, including /app/data/arcane.db (the SQLite database containing every user's password hash and API key), enabling escalation to admin and, via Arcane's Docker control plane, RCE on the host. This vulnerability is fixed in 1.19.4.
Weakness: CWE-22
Which versions are affected by CVE-2026-47179?
3 open source packages ship an affected version, including github.com/getarcaneapp/arcane/backend.
| Package | Affected | Fixed in |
|---|---|---|
github.com/getarcaneapp/arcane/backend Go | All versions | 1.19.4 |
github.com/getarcaneapp/arcane/backend Go | All versions | 1.19.4 |
github.com/getarcaneapp/arcane/backend Go | All versions | 1.19.4 |
How do I fix CVE-2026-47179?
Upgrade github.com/getarcaneapp/arcane/backend to 1.19.4 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-47179 being exploited?
There is no known exploitation of CVE-2026-47179 in the wild and no public exploit code.
Sources
Also known as GHSA-c3px-h233-h6fq, GO-2026-5308.