CVE-2026-96626: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in getarcaneapp arcane
Description
Arcane versions prior to 2.5.0 contain a vulnerability where an attacker with certain registry permissions can cause the system to send a stored encrypted token to an attacker-controlled registry URL. This occurs because the registry URL can be changed without requiring a replacement token, allowing the preserved token to be decrypted and exposed. This can lead to unauthorized access or tampering of container images. The issue is fixed in version 2.5.0.
CVSS v3.1
Score 8.5high
Affected software
getarcaneapp
arcane
pkg:github/getarcaneapp/arcaneRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Arcane, a Docker management interface, has a vulnerability (CVE-2026-96626) in versions before 2.5.0 where the UpdateRegistry and TestRegistry functions allow changing the registry URL while preserving the encrypted token. If an attacker with registries:update and registries:test permissions repoints a generic registry URL without providing a new token, the system decrypts and sends the preserved token to the attacker-controlled host. This is due to the lack of restrictions in normalizeRegistryServerAddressInternal on the destination address. The exposed token can be a container-registry personal access token or password, enabling unauthorized image access or tampering. The vulnerability is resolved in version 2.5.0.
Potential Impact
An attacker with specific registry permissions can obtain sensitive authentication tokens by redirecting registry URLs to attacker-controlled hosts. This exposure can lead to unauthorized access to container images or tampering with them. The confidentiality of stored container-registry personal access tokens or passwords is compromised. There is no indication of impact on availability or integrity beyond image tampering.
Mitigation Recommendations
This vulnerability is fixed in Arcane version 2.5.0. Users should upgrade to version 2.5.0 or later to remediate this issue. No alternative mitigations are indicated in the advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-23T14:35:50.129Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad2989d2cdf04f6563b31ed
Added to database: 10/16/2026, 21:35:25 UTC
Last enriched: 10/16/2026, 21:48:18 UTC
Last updated: 10/16/2026, 21:50:42 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.