# 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.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-c3px-h233-h6fq, GO-2026-5308

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-47179?

3 open source packages ship an affected version, including github.com/getarcaneapp/arcane/backend.


| Package | Ecosystem | 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.

## Is CVE-2026-47179 being exploited?

There is no known exploitation of CVE-2026-47179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47179 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-47179 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.4
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.4
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47179/ (Markdown: https://insights.sbomify.com/CVE-2026-47179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47179
- OSV: https://osv.dev/vulnerability/CVE-2026-47179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47179/
Summaries are generated and may contain mistakes; the official description above is the record.