Skip to main content
CVE-2026-23520VulnerabilityPublished

CVE-2026-23520: getarcaneapp arcane · OS Command Injection

Affects getarcaneapp arcaneSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.13.0 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.13.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Upgrade arcane and getarcaneapp/arcane to 1.13.0.

Affected software

ProductAffectedFixed in
getarcaneapparcaneAffected
  • <1.13.0
Fixed in
  • 1.13.0
GitHubgetarcaneapp/arcanepkg:github/getarcaneapp/arcaneOther threatsAffected
  • <1.13.0
Fixed in
  • 1.13.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Arcane to version 1.13.0 or later immediately to apply the official fix. 2. Restrict project creation permissions to trusted users only, minimizing the risk of malicious lifecycle label injection. 3. Implement strict access controls and monitoring on the Arcane API to detect unauthorized project creations or suspicious lifecycle label usage. 4. Audit and review lifecycle label configurations regularly to ensure no unauthorized commands are present. 5. Limit the privileges of the updater service and container update processes to the minimum necessary to reduce impact if exploited. 6. Establish operational procedures requiring verification before triggering container updates, especially in production environments. 7. Employ runtime security tools to monitor container and host behavior for anomalous command executions. 8. Educate administrators about the risk and signs of exploitation related to lifecycle label abuse. 9. Consider network segmentation to isolate container management services from general user networks. 10. Maintain up-to-date backups and incident response plans to mitigate potential damage from exploitation.

Description

CVE-2026-23520 is a critical OS command injection vulnerability in Arcane versions prior to 1.13.0, a tool for modern Docker management. The flaw exists in the updater service, which executes lifecycle label commands without sanitization, allowing authenticated users to inject arbitrary shell commands. An attacker can create a malicious project with crafted lifecycle labels that execute commands when an administrator triggers a container update. This vulnerability affects confidentiality, integrity, and availability, as arbitrary code execution can lead to full system compromise. It requires authenticated user access but not administrator privileges, and user interaction is needed only when an admin initiates the update. The vulnerability is fixed in version 1.13.0.

References

Community reviews

Loading reviews…