CVE-2026-45625: CWE-862: Missing Authorization in getarcaneapp arcane
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 1.19.0, Arcane's huma-based REST API exposes nine endpoints under /api/customize/git-repositories and /api/git-repositories/sync for managing GitOps source repositories and their stored credentials. Eight of those endpoints (list, create, get, update, delete, test, listBranches, browseFiles) never call the checkAdmin(ctx) helper that every other admin-managed resource (container registries, environments, users, API keys, swarm, settings, system, notifications, events) uses, and the huma authentication middleware deliberately enforces only authentication, not the admin role. As a result, any logged-in user with the default user role can list, create, modify, delete, and test git repository configurations. By repointing an existing repository's URL to an attacker-controlled host while omitting the token/sshKey fields (which UpdateRepository only rewrites when explicitly supplied), the attacker causes Arcane to decrypt the legitimate PAT/SSH key on its next /test, /branches, or /files call and present it as HTTP Basic auth (or SSH key auth) to the attacker's host — producing a one-step exfiltration of plaintext Git credentials. This vulnerability is fixed in 1.19.0.
AI Analysis
Technical Summary
Arcane, a Docker management interface, exposes several GitOps repository management endpoints that fail to enforce admin authorization checks, relying only on authentication. This missing authorization (CWE-862) affects eight endpoints that allow listing, creating, updating, deleting, and testing Git repository configurations by any logged-in user. An attacker can exploit this by changing a repository URL to an attacker-controlled host without updating credentials, causing Arcane to decrypt and send the legitimate credentials during subsequent API calls, effectively leaking plaintext Git credentials. The issue is resolved in version 1.19.0.
Potential Impact
The vulnerability allows any authenticated user with default privileges to gain unauthorized administrative capabilities over GitOps repository configurations. This leads to the exfiltration of plaintext Git credentials (Personal Access Tokens or SSH keys), which can be used to access sensitive source code repositories and potentially escalate further attacks. The CVSS score of 9.9 reflects critical impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Arcane to version 1.19.0 or later, where this authorization flaw is fixed. No official patch links are provided, but the vendor has addressed the issue in the stated version. Until upgraded, restrict access to the Arcane API to trusted users only and monitor for suspicious repository configuration changes. Patch status is not explicitly confirmed beyond the fixed version; verify with vendor advisories for the latest remediation guidance.
CVE-2026-45625: CWE-862: Missing Authorization in getarcaneapp arcane
Description
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 1.19.0, Arcane's huma-based REST API exposes nine endpoints under /api/customize/git-repositories and /api/git-repositories/sync for managing GitOps source repositories and their stored credentials. Eight of those endpoints (list, create, get, update, delete, test, listBranches, browseFiles) never call the checkAdmin(ctx) helper that every other admin-managed resource (container registries, environments, users, API keys, swarm, settings, system, notifications, events) uses, and the huma authentication middleware deliberately enforces only authentication, not the admin role. As a result, any logged-in user with the default user role can list, create, modify, delete, and test git repository configurations. By repointing an existing repository's URL to an attacker-controlled host while omitting the token/sshKey fields (which UpdateRepository only rewrites when explicitly supplied), the attacker causes Arcane to decrypt the legitimate PAT/SSH key on its next /test, /branches, or /files call and present it as HTTP Basic auth (or SSH key auth) to the attacker's host — producing a one-step exfiltration of plaintext Git credentials. This vulnerability is fixed in 1.19.0.
CVSS v3.1
Score 9.9critical
Affected software
pkg:github/getarcaneapp/arcaneRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Arcane, a Docker management interface, exposes several GitOps repository management endpoints that fail to enforce admin authorization checks, relying only on authentication. This missing authorization (CWE-862) affects eight endpoints that allow listing, creating, updating, deleting, and testing Git repository configurations by any logged-in user. An attacker can exploit this by changing a repository URL to an attacker-controlled host without updating credentials, causing Arcane to decrypt and send the legitimate credentials during subsequent API calls, effectively leaking plaintext Git credentials. The issue is resolved in version 1.19.0.
Potential Impact
The vulnerability allows any authenticated user with default privileges to gain unauthorized administrative capabilities over GitOps repository configurations. This leads to the exfiltration of plaintext Git credentials (Personal Access Tokens or SSH keys), which can be used to access sensitive source code repositories and potentially escalate further attacks. The CVSS score of 9.9 reflects critical impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Arcane to version 1.19.0 or later, where this authorization flaw is fixed. No official patch links are provided, but the vendor has addressed the issue in the stated version. Until upgraded, restrict access to the Arcane API to trusted users only and monitor for suspicious repository configuration changes. Patch status is not explicitly confirmed beyond the fixed version; verify with vendor advisories for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-12T20:31:43.449Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a19cdf2e29bf47b50fb4708
Added to database: 05/29/2026, 17:33:38 UTC
Last enriched: 06/05/2026, 21:02:51 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 88
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.
External Links
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.