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

> A user with delegated update permissions can reset the global administrator's password, leading to complete account takeover and privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-pw5q-rjx4-7f7p, GO-2026-6807

## What is CVE-2026-96627?

CVE-2026-96627 is a high-severity vulnerability in getarcaneapp arcane, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 2.6.0, UpdateUser in backend/api/handlers/users.go sets PasswordHash for any target without comparing caller and target privilege. A holder of delegated users:update permission can submit a password change for the global administrator, replace the administrator password, and authenticate as that account, resulting in complete global administrator account takeover. This issue is fixed in version 2.6.0.

Weakness: CWE-269 (Improper Privilege Management), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-96627?

4 open source packages ship an affected version, including github.com/getarcaneapp/arcane/backend/v2 and github.com/getarcaneapp/arcane/backend.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/getarcaneapp/arcane/backend/v2` | Go | All versions | 2.6.0 |
| `github.com/getarcaneapp/arcane/backend/v2` | Go | All versions | 2.6.0 |
| `github.com/getarcaneapp/arcane/backend/v2` | Go | All versions | 2.6.0 |
| `github.com/getarcaneapp/arcane/backend` | Go | All versions | None |

## How do I fix CVE-2026-96627?

Upgrade github.com/getarcaneapp/arcane/backend/v2 to 2.6.0 or later.

## Is CVE-2026-96627 being exploited?

There is no known exploitation of CVE-2026-96627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96627 and fix it if it is affected.

What it is: CVE-2026-96627 is a high-severity vulnerability in getarcaneapp arcane, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96627 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/getarcaneapp/arcane/backend/v2 (Go): affected all versions; fixed in 2.6.0
- github.com/getarcaneapp/arcane/backend/v2 (Go): affected all versions; fixed in 2.6.0
- github.com/getarcaneapp/arcane/backend/v2 (Go): affected all versions; fixed in 2.6.0
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96627/ (Markdown: https://insights.sbomify.com/CVE-2026-96627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96627
- OSV: https://osv.dev/vulnerability/CVE-2026-96627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96627/
Summaries are generated and may contain mistakes; the official description above is the record.