CVE-2026-45626: Arcane: OS Command Injection in Volume Browser ListDirectory via path query parameter
Arcane is an interface for managing Docker containers, images, networks, and volumes. In 1.18.1 and earlier, GET /environments/{id}/volumes/{volumeName}/browse accepts a path query parameter that is passed to a shell command (sh -c "find … | while …") inside an Arcane helper container. The path sanitiser blocks ../ traversal but does not strip Bourne-shell metacharacters such as $() or backticks, and strconv.Quote only escapes Go string metacharacters, not shell substitution sequences. Any authenticated user with access to a browseable volume can execute arbitrary commands inside the helper container; command output is reflected back in the 500 error body.
Security readout for executives and security teams
Plain-English summary
Arcane has a command injection flaw in its Docker volume browsing feature. A logged-in user with access to a browseable volume could make Arcane run unintended commands inside a helper container. This is not reported as remotely exploitable without credentials, but it can affect confidentiality, integrity, and availability within that container context.
Executive priority
Treat this as a prompt administrative remediation item, not a crisis. Prioritize Arcane instances with broad user access or sensitive Docker environments, because authenticated users could abuse management functionality to run unintended commands in a helper container.
Technical view
In Arcane 1.18.1 and earlier, the volume browse endpoint passes the path query parameter into a shell command. The sanitizer blocks path traversal but not shell substitution syntax. An authenticated user with volume browse access can execute commands inside the helper container, with some output reflected in error responses. CVSS is 6.3, CWE-78.
Likely exposure
Exposure is likely limited to organizations running Arcane 1.18.1 or earlier where authenticated users can browse Docker volumes. Risk increases if Arcane is reachable by many users, internet-accessible behind login, or managing sensitive container environments.
Exploitation context
The provided sources do not cite active exploitation, and this CVE is not marked KEV. Exploitation requires authentication and access to a browseable volume. The impact is described inside Arcane’s helper container, not as direct host compromise in the provided evidence.
Researcher notes
Evidence is centered on the GitHub security advisory and CVE record. The affected component is GET /environments/{id}/volumes/{volumeName}/browse via the path query parameter. Sources do not provide a fixed version, active exploitation evidence, or direct host escape impact.
Mitigation direction
Check the GitHub advisory and vendor release notes for patched Arcane versions or official workarounds.
Restrict Arcane access to trusted administrators until remediation is confirmed.
Limit volume browsing permissions for nonessential users.
Review helper container privileges and reduce access to sensitive Docker resources where possible.
Monitor browse endpoint errors and helper-container activity for suspicious behavior.
Validation and detection
Inventory Arcane deployments and confirm whether any run version 1.18.1 or earlier.
Identify users or roles allowed to browse Docker volumes in Arcane.
Confirm whether Arcane is reachable from the internet or broad internal networks.
Review logs for unusual volume browse requests and repeated 500 responses.
Validate remediation against vendor guidance in a non-production environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.