How severe is GHSA-gjqq-6r35-w3r8?

GHSA-gjqq-6r35-w3r8 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gjqq-6r35-w3r8?

GHSA-gjqq-6r35-w3r8 affects the following packages: github.com/getarcaneapp/arcane/backend (Go). Ecosystems affected: Go.

How do I fix GHSA-gjqq-6r35-w3r8?

Update github.com/getarcaneapp/arcane/backend to 0.0.0-20260114065515-5a9c2f92e11f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gjqq-6r35-w3r8 is resolved across your whole dependency graph.

How do I detect GHSA-gjqq-6r35-w3r8 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/getarcaneapp/arcane/backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gjqq-6r35-w3r8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gjqq-6r35-w3r8?

O3 pinpoints whether GHSA-gjqq-6r35-w3r8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gjqq-6r35-w3r8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gjqq-6r35-w3r8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gjqq-6r35-w3r8?

GHSA-gjqq-6r35-w3r8 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gjqq-6r35-w3r8?

GHSA-gjqq-6r35-w3r8 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-gjqq-6r35-w3r8 published, and has it been updated?

GHSA-gjqq-6r35-w3r8 was published on January 15, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-gjqq-6r35-w3r8

CRITICAL

Arcane Has a Command Injection in Arcane Updater Lifecycle Labels That Enables RCE

Also known asCVE-2026-23520GO-2026-4320

Published

Jan 15, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk73th percentile+1.60%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/getarcaneapp/arcane/backend

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

If the container is configured with host volume mounts in its Compose definition, the executed command may be able to read from or write to the host filesystem through the mounted paths. This can enable data theft and, in some configurations, escalation to full host compromise (for example, if /var/run/docker.sock is mounted).

Impact

Remote code execution (RCE) within the updated container context.
Host filesystem access when host volumes are mounted into the container.
Potential data exfiltration via outbound network requests or by exposing readable files.
Potential full host compromise if sensitive mounts are present (e.g., /var/run/docker.sock).

Patches

The lifecycle labels com.getarcaneapp.arcane.lifecycle.pre-update and com.getarcaneapp.arcane.lifecycle.post-update have been removed to eliminate this attack surface.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/getarcaneapp/arcane/backend`	all versions	0.0.0-20260114065515-5a9c2f92e11f

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/getarcaneapp/arcane/backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/getarcaneapp/arcane/backend to 0.0.0-20260114065515-5a9c2f92e11f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gjqq-6r35-w3r8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gjqq-6r35-w3r8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gjqq-6r35-w3r8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary 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

O3 Security · Impact-Aware SCA

Is GHSA-gjqq-6r35-w3r8 in your dependencies?

O3 detects GHSA-gjqq-6r35-w3r8 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works