Vulnerability in github.com/getarcaneapp/arcane/backend (CVE-2026-45625)
Summary
Vulnerability in github.com/getarcaneapp/arcane/backend (CVE-2026-45625). Successful exploitation can lead to full system takeover. Exploitable via PUT /customize/git-repositories/{id}. Mitigation: upgrade to 1.19.0 or later.
Original description
The description as published by the source.
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 1.19.0, Arcane's huma-based REST API exposes nine endpoints under /api/customize/git-repositories and /api/git-repositories/sync for managing GitOps source repositories and their stored credentials. Eight of those endpoints (list, create, get, update, delete, test, listBranches, browseFiles) never call the checkAdmin(ctx) helper that every other admin-managed resource (container registries, environments, users, API keys, swarm, settings, system, notifications, events) uses, and the huma authentication middleware deliberately enforces only authentication, not the admin role. As a result, any logged-in user with the default user role can list, create, modify, delete, and test git repository configurations. By repointing an existing repository's URL to an attacker-controlled host while omitting the token/sshKey fields (which UpdateRepository only rewrites when explicitly supplied), the attacker causes Arcane to decrypt the legitimate PAT/SSH key on its next /test, /branches, or /files call and present it as HTTP Basic auth (or SSH key auth) to the attacker's host — producing a one-step exfiltration of plaintext Git credentials. This vulnerability is fixed in 1.19.0.
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-45625 has been found in github.com/getarcaneapp/arcane/backend.
Attackers can target a specific entry point like PUT /customize/git-repositories/{id} over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/getarcaneapp/arcane/backend to 1.19.0 or later.
If unsure, ask your IT team or search "github.com/getarcaneapp/arcane/backend CVE-2026-45625" on the vendor's site.
CVE-2026-45625 (github.com/getarcaneapp/arcane/backend) — CWE-862 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /customize/git-repositories/{id} / GET /api/customize/git-repositories / PUT /api/customize/git-repositories/{id} / POST /api/customize/git-repositories/{id}/test
Patched: 1.19.0 — apply immediately
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.
A vulnerability (CWE-862) exists in github.com/getarcaneapp/arcane/backend. Attackers reach the vulnerable code path via PUT /customize/git-repositories/{id}.
Check the vendor advisory for the affected versions of github.com/getarcaneapp/arcane/backend. Attack surface: PUT /customize/git-repositories/{id} / GET /api/customize/git-repositories / PUT /api/customize/git-repositories/{id} / POST /api/customize/git-repositories/{id}/test.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 1.19.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /customize/git-repositories/{id} 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 'PUT /customize/git-repositories/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /customize/git-repositories/{id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/getarcaneapp/arcane/backend to 1.19.0ステージング環境で 1.19.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PUT /customize/git-repositories/{id} 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