Arcane Has an Authenticated Arbitrary Host File Read via Docker Compose Include Directives

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-47179: 0.31% estimated exploitation activity in the next 30 days; percentile 23.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details Root cause #1 — CreateProject writes compose content without validation (backend/internal/services/projectservice.go:1605-1644): Compare with UpdateProject (projectservice.go:2494, :2577), which calls validateComposeContentForUpdate. That validator (line…

Published by the source

28 May 2026, 22:39 UTC

Last modified by the source

9 Jun 2026, 10:30 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c3px-h233-h6fq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47179

Advisory: Arcane Has an Authenticated Arbitrary Host File Read via Docker Compose Include Directives
IDs: CVE-2026-47179, GHSA-c3px-h233-h6fq
Record: https://patchnext.com/advisories/cve-2026-47179 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/getarcaneapp/arcane/backend 1.19.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/getarcaneapp/arcane/backend: affected <= 1.19.3; fixed in 1.19.4

## Suggested inspection (read-only)
- Go github.com/getarcaneapp/arcane/backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/getarcaneapp/arcane/backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c3px-h233-h6fq (GitHub-reviewed advisory GHSA-c3px-h233-h6fq lists affected ranges: Go github.com/getarcaneapp/arcane/backend >=0 <=1.19.3)

Commands are suggestions: review each one before running it.