high · 8.8 Patched

Arcane: Delegated users:update permission allows admin account takeover via password reset (no privilege-hierarchy check)

CVE-2026-96627 · GHSA-pw5q-rjx4-7f7p · GO-2026-6807 · published 16 Oct 2026

How serious is it

  • Severity: high, CVSS score 8.8 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-96627?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • github.com/getarcaneapp/arcane/backend/v2 (Go) < 2.6.0

How to check

  1. Run go list -m github.com/getarcaneapp/arcane/backend/v2 in your project to see the installed version, including copies pulled in by other packages.
  2. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. Upgrade github.com/getarcaneapp/arcane/backend/v2 to 2.6.0 or later, commit the lockfile and redeploy.
  2. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

## 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.Save`s — 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 `RequireGlobalAdmin`. Bypass: intended delegation (holder is meant to manage profiles, not seize admin). 2. Action: `PUT /users/{adminId}` `{"password":"attacker123"}`. Guard: `RequirePermission(users:update)` (`users.go:154`). Bypass: holder has it; no hierarchy check (`users.go:317-323`, `user_service.go:174` unconditional Save). 3. Action: `POST /auth/login` as admin → admin session. ## Bypass Evidence - `users.go:317-323` sets `PasswordHash` for any target; `user_service.go:174-194` has no actor/target privilege comparison. - Only `IsGlobalAdmin` hits are `DeleteUser`'s last-admin guard and DTO flags (grep). - `users:update` is org-level, held by no built-in non-admin role (`permissions.go:24`). ## Affected Versions `<= 2.5.0`. Reported by **zx (Jace)** — GitHub: @manus-use

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 23 Oct 2026. All vulnerabilities · RSS · JSON