# CVE-2026-45625: Arcane Backend: Missing admin authorization on git repository endpoints allows non-admin users to exfiltrate stored Git credentials and tamper with GitOps configs

> Non-admin users can access Git repository endpoints to exfiltrate stored credentials and tamper with GitOps configurations due to missing authorization checks.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 29 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-7h26-hg47-p9hx, GO-2026-5220

## What is CVE-2026-45625?

CVE-2026-45625 is a critical missing authorization vulnerability in getarcaneapp arcane, published on 29 May 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 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.

Weakness: CWE-862 (Missing Authorization)

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

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


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

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

Upgrade github.com/getarcaneapp/arcane/backend to 1.19.0 or later.

## Is CVE-2026-45625 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45625 is a critical missing authorization vulnerability in getarcaneapp arcane, published on 29 May 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-45625 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.0
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.0
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.0

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-45625/ (Markdown: https://insights.sbomify.com/CVE-2026-45625/index.md)
```

## Sources

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

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