Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-96627 high CVSS 8.8

Vulnerability in github.com/getarcaneapp/arcane/backend/v2 (CVE-2026-96627)

Summary

Vulnerability in github.com/getarcaneapp/arcane/backend/v2 (CVE-2026-96627). Successful exploitation can lead to full system takeover. Exploitable via PUT /users/{adminId}. Mitigation: upgrade to 2.6.0 or later.

Original description

The description as published by the source.

Summary

A user holding the delegated users:update permission can reset the global administrator's password and take over the admin account. UpdateUser sets the target user's PasswordHash from the request body for ANY target with no comparison of caller-vs-target privilege. Because role assignment and role CRUD are deliberately gated by RequireGlobalAdmin, users:update is intended to sit BELOW admin (profile management); this finding defeats that separation.

Root Cause

UpdateUser (handler backend/api/handlers/users.go:317-323) loads the target by ID and sets userModel.PasswordHash from the request body for any user, then userService.UpdateUser (user_service.go:174) simply tx.Saves — with NO actor-vs-target privilege comparison. The only IsGlobalAdmin guard (user_service.go:345) is a last-admin check inside DeleteUser, not the update path. Role assignment / role CRUD are RequireGlobalAdmin (backend/pkg/authz/permissions.go:27-33), proving users:update is intended below admin.

Impact

Complete administrator account takeover (C:H/I:H/A:H) by any holder of the delegated users:update permission.

Proof of Concept

  1. Admin delegates a custom "User Manager" role with users:update.
  2. PUT /users/{adminId} with {"password":"attacker123"}.
  3. POST /auth/login {"username":"arcane","password":"attacker123"} → admin session.

Attack Chain

  1. Action: admin delegates custom role with users:update. Guard: role creation is `RequireG…

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-96627 has been found in github.com/getarcaneapp/arcane/backend/v2.
Attackers can target a specific entry point like PUT /users/{adminId} over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/getarcaneapp/arcane/backend/v2 to 2.6.0 or later.
If unsure, ask your IT team or search "github.com/getarcaneapp/arcane/backend/v2 CVE-2026-96627" on the vendor's site.

CVE-2026-96627 (github.com/getarcaneapp/arcane/backend/v2) — CWE-266 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /users/{adminId} / POST /auth/login / UpdateUser / PasswordHash
Patched: 2.6.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.

❓ What is the problem

A vulnerability (CWE-266) exists in github.com/getarcaneapp/arcane/backend/v2. Attackers reach the vulnerable code path via PUT /users/{adminId}.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/getarcaneapp/arcane/backend/v2. Attack surface: PUT /users/{adminId} / POST /auth/login / UpdateUser / PasswordHash.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.6.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual PUT /users/{adminId} requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/getarcaneapp/arcane/backend/v2' . 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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/getarcaneapp/arcane/backend/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/getarcaneapp/arcane/backend/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PUT /users/{adminId}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PUT /users/{adminId} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/getarcaneapp/arcane/backend/v2 to 2.6.0

    ステージング環境で 2.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against PUT /users/{adminId} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/getarcaneapp/arcane/backend/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.6.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details