Arcane has a Command Injection in Arcane Updater Lifecycle Labels Enables RCE
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-23520
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 15:30 UTC · Revision 1
Source evidence
Arcane has a Command Injection in Arcane Updater Lifecycle Labels Enables RCE
core-osv · Original sourcePublished 15 Jan 2026, 19:20 UTC
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.
osv:CVE-2026-23520
Complete source record
{
"id": "44993f6aa7cf719749382b6d1ac0cde179e9b551e81f428ccdd8cb82c6d5f04e",
"url": "https://osv.dev/vulnerability/CVE-2026-23520",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Arcane has a Command Injection in Arcane Updater Lifecycle Labels Enables RCE",
"summary": "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.",
"evidence": "osv:CVE-2026-23520",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-23520",
"aliases": [
"CVE-2026-23520",
"GHSA-gjqq-6r35-w3r8",
"GO-2026-4320"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/getarcaneapp/arcane",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "2e32ef4443676edcceb26c8e41f637974f0041c8"
},
{
"fixed": "5a9c2f92e11f86f8997da8c672844468f930b7e4"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:arcane:arcane:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.13.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "5a9c2f92e11f86f8997da8c672844468f930b7e4"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "2e32ef4443676edcceb26c8e41f637974f0041c8"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v1.13.0"
}
]
}
}
],
"versions": [
"v1.12.2",
"v1.12.1",
"v1.12.0",
"v1.11.3",
"v1.11.2",
"v1.11.1",
"v1.11.0",
"v1.10.1",
"v1.10.0",
"v1.9.0",
"v1.8.1",
"v1.8.0",
"v1.7.1",
"v1.7.0",
"v1.6.0",
"v1.5.2",
"v1.5.1",
"v1.5.0",
"v1.4.0",
"v1.3.0",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.0",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v0.15.1",
"v0.15.0",
"v0.14.0",
"v0.13.1",
"v0.13.0",
"v0.12.0",
"v0.11.1",
"v0.11.0",
"v0.10.0",
"v0.9.2",
"v0.9.1",
"v0.9.0",
"v0.8.0",
"v0.7.1",
"v0.7.0",
"v0.6.0",
"v0.5.0",
"v0.4.1",
"v0.4.0",
"v0.3.0",
"v0.2.0",
"v0.1.1",
"v0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23520.json"
}
}
],
"modified": "2026-10-28T02:30:36.998741865Z",
"provider": "osv",
"references": [
"https://github.com/getarcaneapp/arcane/releases/tag/v1.13.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23520.json",
"https://github.com/getarcaneapp/arcane/security/advisories/GHSA-gjqq-6r35-w3r8",
"https://nvd.nist.gov/vuln/detail/CVE-2026-23520",
"https://github.com/getarcaneapp/arcane/commit/5a9c2f92e11f86f8997da8c672844468f930b7e4",
"https://github.com/getarcaneapp/arcane/pull/1468"
],
"provider_metadata": {
"cwe_ids": [
"CWE-78"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23520.json"
}
},
"related_cves": [
{
"value": "CVE-2026-23520",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 504143,
"published_at": "2026-01-15T19:20:22.434+00:00"
}