---
id: "CVE-2026-96626"
kind: "vulnerability"
aliases: ["CVE-2026-96626"]
title: "Arcane: registry URL change leaks stored container registry token"
severity: "high"
cvss: 8.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["arcane", "container-registry", "docker", "package", "self-hosted"]
not_affected_if: ["arcane-2.5.0-or-later", "no-generic-registries", "trusted-registry-admins"]
published_at: "2026-10-16T22:18:58+00:00"
first_seen_at: "2026-10-23T21:57:14+00:00"
updated_at: "2026-10-25T03:01:35+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-96626", "first_seen_at": "2026-10-23T21:57:14+00:00"}]
---

# Arcane: registry URL change leaks stored container registry token

Arcane, a Docker management interface, lets a user with registry update and test permissions repoint a stored registry URL while keeping the saved token. The test then sends that decrypted token to the attacker-chosen host, exposing the registry password or PAT and enabling image access or tampering.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Arcane version; releases before `2.5.0` are affected.
- Review which users hold `registries:update` and `registries:test` permissions in Arcane.

## Fix

- Upgrade Arcane to `2.5.0` or later.
- Rotate the stored container registry tokens and passwords after upgrading if the registry permissions were held by untrusted users.

## Timeline

- 2026-10-23T21:57:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-96626

## From the sources

Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 2.5.0, UpdateRegistry and TestRegistry in backend/api/services/container_registry_service.go allow the registry URL to change while preserving the stored encrypted token. When a holder of registries:update and registries:test repoints a generic registry URL without supplying a replacement token, TestRegistry decrypts the preserved token and RegistryLogin sends it to the attacker-controlled host because normalizeRegistryServerAddressInternal does not restrict the destination. This exposes the stored container-registry PAT or password and can enable image access or tampering. This issue is fixed in version 2.5.0.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_