OS Command Injection in github.com/getarcaneapp/arcane/backend (CVE-2026-45626)
Summary
OS command injection in github.com/getarcaneapp/arcane/backend (CVE-2026-45626). Risk of unauthorized operations or information disclosure. Exploitable via GET /environments/{id}/volumes/{volumeName}/browse.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45626 has been found in github.com/getarcaneapp/arcane/backend.
Attackers can target a specific entry point like GET /environments/{id}/volumes/{volumeName}/browse over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/getarcaneapp/arcane/backend CVE-2026-45626" on the vendor's site.
CVE-2026-45626 (github.com/getarcaneapp/arcane/backend) — CWE-78 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /environments/{id}/volumes/{volumeName}/browse / DELETE /environments/{id}/volumes/{volumeName}/browse / path / strconv.Quote
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in github.com/getarcaneapp/arcane/backend. Attackers reach the vulnerable code path via GET /environments/{id}/volumes/{volumeName}/browse.
Check the vendor advisory for the affected versions of github.com/getarcaneapp/arcane/backend. Attack surface: GET /environments/{id}/volumes/{volumeName}/browse / DELETE /environments/{id}/volumes/{volumeName}/browse / path / strconv.Quote.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /environments/{id}/volumes/{volumeName}/browse requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/getarcaneapp/arcane/backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/getarcaneapp/arcane/backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/getarcaneapp/arcane/backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /environments/{id}/volumes/{volumeName}/browse' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /environments/{id}/volumes/{volumeName}/browseへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /environments/{id}/volumes/{volumeName}/browse on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com