Security readout for executives and security teams
Plain-English summary
Arcane before 1.13.0 lets a low-privileged authenticated user set update lifecycle labels that later cause shell commands to run when an administrator updates a container. This can turn ordinary project creation access into remote code execution inside the container.
Executive priority
Treat as urgent for any shared Arcane environment. A normal authenticated user could cause code execution during routine updates, creating high confidentiality, integrity, and availability risk. Prioritize upgrade and access review before further scheduled updates where feasible.
Technical view
CVE-2026-23520 is CWE-78 command injection in Arcane’s updater service. Values from com.getarcaneapp.arcane.lifecycle.pre-update and post-update labels are passed to /bin/sh -c without sanitization. Any authenticated API user can create a project with such labels; execution occurs when an admin or scheduled process triggers container updates.
Likely exposure
Organizations running getarcaneapp Arcane versions earlier than 1.13.0 are affected, especially where multiple authenticated users can create projects through the API. Exposure depends on whether untrusted or lower-privileged users have Arcane accounts and whether container updates are performed manually or scheduled.
Exploitation context
The advisory indicates exploitation requires authenticated access and a later update action by an administrator or scheduled update process. The CVSS vector is network, low complexity, low privileges, and user interaction required. The source bundle does not show CISA KEV listing or confirmed active exploitation.
Researcher notes
The key trust-boundary issue is that user-controlled lifecycle label values reach shell execution in the updater path. The vendor states the issue is fixed in 1.13.0. Public sources provided do not establish exploitation in the wild or impact beyond execution inside the container.
Mitigation direction
- Upgrade Arcane to version 1.13.0 or later.
- Review vendor advisory and release notes for any additional hardening guidance.
- Restrict project creation to trusted users until upgraded.
- Review existing projects for updater lifecycle labels before triggering updates.
- Audit recent Arcane project changes by non-administrative users.
Validation and detection
- Inventory Arcane deployments and confirm version is below or at least 1.13.0.
- Check whether authenticated non-admin users can create projects through the API.
- Inspect project/container metadata for the documented pre-update and post-update lifecycle labels.
- Review update schedules and recent administrator-triggered container updates.
- Confirm the 1.13.0 fix is deployed in production and backups.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23520 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H2.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/getarcaneapp/arcane/security/advisories/GHSA-gjqq-6r35-w3r8CVE reference · x_refsource_CONFIRM
- https://github.com/getarcaneapp/arcane/pull/1468CVE reference · x_refsource_MISC
- https://github.com/getarcaneapp/arcane/commit/5a9c2f92e11f86f8997da8c672844468f930b7e4CVE reference · x_refsource_MISC
- https://github.com/getarcaneapp/arcane/releases/tag/v1.13.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.