getarcaneapp arcane up to 1.19.3 Project File API ProjectService.CreateProject path traversal

Summaryinfo

A vulnerability was found in getarcaneapp arcane up to 1.19.3. It has been classified as critical. Affected by this vulnerability is the function ProjectService.CreateProject of the component Project File API. Performing a manipulation results in path traversal. This vulnerability was named CVE-2026-47179. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in getarcaneapp arcane up to 1.19.3. It has been classified as critical. This affects the function ProjectService.CreateProject of the component Project File API. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-47179 since 05/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 1.19.4 eliminates this vulnerability. Applying the patch b6cbffabf61dbc3f12a28d3b5830e3c6b7e67daf is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• getarcaneapp

Name

• arcane

Version

• 1.19.0
• 1.19.1
• 1.19.2
• 1.19.3

License

• open-source

Website

• Product: https://github.com/getarcaneapp/arcane/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion