CVE-2026-96626
Arcane is an interface for managing Docker containers, images, …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/getarcaneapp/arcane/commit/fe31693634f48f295a7d77d091085b331cf9e915
- github.com/getarcaneapp/arcane/pull/3317
- github.com/getarcaneapp/arcane/releases/tag/backend/v2.5.0
- github.com/getarcaneapp/arcane/security/advisories/GHSA-9pxc-cxp5-qp54
- nvd.nist.gov/vuln/detail/CVE-2026-96626
- cve.org/CVERecord?id=CVE-2026-96626
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.