CVE Tools
Track your stack

CVE-2026-23520

Arcane has a Command Injection in Arcane Updater Lifecycle Labels Enables RCE

No known exploitation. EPSS puts it in the 79th percentile. Fixed versions are out.

CVSS 3.19.0CriticalEPSS percentile79th1.8% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix4 products2 fixed builds listed below

Published Updated Sources: CVE.org, NVD, GitHub, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Getarcaneapp ArcaneAffected: < 1.13.0Upgrade to: not statedStated by: CVE record
  • Go github.com/getarcaneapp/arcane/backendAffected: < 0.0.0-20260114065515-5a9c2f92e11fUpgrade to: 0.0.0-20260114065515-5a9c2f92e11fStated by: GitHub advisory
  • ArcaneAffected: < 1.13.0Upgrade to: 1.13.0Stated by: NVD
  • Сообщество свободного программного обеспечения ArcaneAffected: до 1.13.0Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Arcane provides modern docker management. Prior to 1.13.0, Arcane has a command injection in the updater service. Arcane’s updater service supported lifecycle labels com.getarcaneapp.arcane.lifecycle.pre-update and com.getarcaneapp.arcane.lifecycle.post-update that allowed defining a command to run before or after a container update. The label value is passed directly to /bin/sh -c without sanitization or validation. Because any authenticated user (not limited to administrators) can create projects through the API, an attacker can create a project that specifies one of these lifecycle labels with a malicious command. When an administrator later triggers a container update (either manually or via scheduled update checks), Arcane reads the lifecycle label and executes its value as a shell command inside the container. This vulnerability is fixed in 1.13.0.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS79th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.8% chance of exploitation activity in the next 30 days, which ranks it in the 79th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 21 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Scored 9.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 6 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Arcane, not every advisory.