CVE-2026-23944: getarcaneapp arcane · Missing Authentication
Affects getarcaneapp arcaneSource CVE Database V5
Not known to be exploited · CVSS 8.0 High : upgrade to 1.13.2 soon.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.13.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade arcane and getarcaneapp/arcane to 1.13.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getarcaneapparcane | Affected
| Fixed in
|
GitHubgetarcaneapp/arcanepkg:github/getarcaneapp/arcaneOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade Arcane to version 1.13.2 or later to remediate this vulnerability. Until patching is complete, organizations should restrict network access to Arcane management interfaces by implementing strict firewall rules and network segmentation to limit exposure to trusted internal networks only. Employing zero-trust network principles can reduce the risk of unauthorized access. Monitoring and logging of all API requests to Arcane should be enhanced to detect anomalous or unauthorized activities, particularly requests to `/api/environments/{id}/...` endpoints. Organizations should audit their current deployment architectures to identify any remote environment agents accessible via Arcane and verify that no unauthorized access has occurred. Additionally, consider implementing multi-factor authentication (MFA) and role-based access controls (RBAC) around management interfaces to add layers of security. Regular vulnerability scanning and penetration testing focused on container management tools can help identify similar issues proactively.
Description
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to version 1.13.2, unauthenticated requests could be proxied to remote environment agents, allowing access to remote environment resources without authentication. The environment proxy middleware handled `/api/environments/{id}/...` requests for remote environments before authentication was enforced. When the environment ID was not local, the middleware proxied the request and attached the manager-held agent token, even if the caller was unauthenticated. This enabled unauthenticated access to remote environment operations (e.g., listing containers, streaming logs, or other agent endpoints). An unauthenticated attacker could access and manipulate remote environment resources via the proxy, potentially leading to data exposure, unauthorized changes, or service disruption. Version 1.13.2 patches the vulnerability.
References
- github.com/getarcaneapp/arcane/security/advisories/GHSA-2jv8-39rp-cqqr (opens in a new tab)
- github.com/getarcaneapp/arcane/pull/1532 (opens in a new tab)
- github.com/getarcaneapp/arcane/commit/2008e1b93b25d0c4c3fff3af07843766231614eb (opens in a new tab)
- github.com/getarcaneapp/arcane/releases/tag/v1.13.2 (opens in a new tab)