Arcane: repointing a registry URL leaks the stored registry credential to an attacker-controlled host

Impact

UpdateRegistry and TestRegistry let the registry URL be changed while keeping the stored encrypted token. A user holding registries:update and registries:test can repoint a generic registry to a host they control without supplying a replacement token; TestRegistry then decrypts the preserved token and RegistryLogin sends it to that host, because normalizeRegistryServerAddressInternal does not restrict the destination. The operator loses the container-registry PAT or password in cleartext to an outside party, which in turn allows pulling private images or pushing tampered ones. For a fleet that pulls its CUDA base images, model-serving images or node bootstrap images from that registry, a tampered image is code execution on GPU nodes at the next rollout, so credential rotation alone is not the end of the cleanup.

Who can reach it

Authenticated user of the Arcane web interface holding the registries:update and registries:test permissions; reachable over the network wherever Arcane is exposed. No access to the registry itself is needed.

What to do

Upgrade Arcane to 2.5.0 (backend/v2.5.0), which is the published fix, and restart the service. Then rotate every registry PAT or password stored in Arcane, since a prior exploitation would already have exfiltrated them, and audit the registry for unexpected pushes or pulls. Restrict registries:update and registries:test to administrators in the meantime.

References

Related entries

• Docker / moby: Command execution via crafted remote git build path in `docker build`CVE-2019-13139 · Docker / mobyHigh
• Rancher: Sensitive data leaked into Rancher audit logsCVE-2023-22649 · RancherHigh
• runc: Insufficient checks when bind-mounting /dev/console allow writes to arbitrary host procfs pathsCVE-2025-52565 · runcHigh
• BuildKit: Custom frontend can craft an API message causing daemon compromiseCVE-2026-33747 · BuildKitHigh
• Helm: Crafted plugin writes its contents to an arbitrary filesystem location on install or updateCVE-2026-35204 · HelmHigh
• Helm: Helm installs plugins with no provenance file even when signature verification is requiredCVE-2026-35205 · HelmHigh