CVE-2026-96626

Deferred Deferred - Pending Action

Remote Code Execution in Arcane Docker Management Interface

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-16

Last Modified

2026-10-16

Generated

2026-10-17

AI Q&A

2026-10-17

EPSS Evaluated

N/A

NVD

CVE-2026-96626

Affected Vendors & Products

Vendor	Product	Version / Range
getarcaneapp	arcane	< 2.5.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-522	The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
CWE-200	The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

Executive Summary

This vulnerability in Arcane before version 2.5.0 allows an attacker with registries:update and registries:test permissions to change a registry URL without providing a new token. The system preserves and decrypts the old token, sending it to the attacker-controlled registry address. This exposes stored container registry credentials like PAT or passwords, enabling unauthorized image access or tampering.

Detection Guidance

To detect this vulnerability, check if Arcane is running a version prior to 2.5.0. Inspect registry URLs for unauthorized changes and verify if stored tokens are being sent to unexpected hosts. Monitor network traffic for registry login attempts to untrusted endpoints.

Impact Analysis

If exploited, this vulnerability could lead to unauthorized access to your container images, potential data theft, or malicious modifications to your images. Attackers could pull sensitive images, inject malware, or disrupt operations by tampering with your container registry contents.

Compliance Impact

This vulnerability exposes stored container-registry credentials (PAT or password) due to improper registry URL handling. For GDPR, this could lead to unauthorized access to personal data processed via compromised container images. Under HIPAA, it may risk exposure of protected health information if registry images contain PHI. Unauthorized image tampering could also violate integrity requirements in both standards.

Mitigation Strategies

Upgrade Arcane to version 2.5.0 or later to address the vulnerability. Review registry configurations to ensure no unauthorized changes were made and tokens were not exposed.

Hi! I’m here to help you understand CVE-2026-96626. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70