dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45626

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Arcane is an interface for managing Docker containers, images, networks, and volumes. In 1.18.1 and earlier, GET /environments/{id}/volumes/{volumeName}/browse accepts a path query parameter that is passed to a shell command (sh -c "find … | while …") inside an Arcane helper container. The path sanitiser blocks ../ traversal but does not strip Bourne-shell metacharacters such as $() or backticks, and strconv.Quote only escapes Go string metacharacters, not shell substitution sequences. Any authenticated user with access to a browseable volume can execute arbitrary commands inside the helper container; command output is reflected back in the 500 error body.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in Arcane's volume browse endpoint allows authenticated users to inject shell metacharacters ($(), backticks) into a path parameter that gets passed to a shell command (sh -c 'find ... | while ...') inside a helper container. The existing path sanitizer only blocks directory traversal but fails to strip shell substitution sequences, enabling arbitrary command execution within the helper container.

MitigationImplement proper shell metacharacter escaping or use exec.Command with separate arguments instead of shell execution to prevent command injection in the path parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Arcane Docker management interface version
    Locate the installed Arcane application and retrieve its version number (typically via --version flag, a version file, or the web interface footer). Compare this to the affected range: versions 1.18.1 and earlier.
    Affected if The installed version is 1.18.1 or any earlier version.
  2. Confirm volume browse endpoint is accessible
    Verify that the volume browse functionality is enabled and reachable. This may involve checking application configuration files or attempting to access the endpoint (e.g., /volume/browse or similar path) if you have administrative access.
    Affected if The volume browse endpoint is enabled and accessible to authenticated users.
  3. Verify authentication configuration for the API
    Check the authentication settings for the Arcane management interface. Determine whether authentication is required for API endpoints, particularly the volume browse functionality.
    Affected if Authentication is disabled or weak, allowing unauthenticated or low-privilege users to reach the volume browse endpoint.
  4. Inspect shell command usage in volume browse code
    If you have access to the source code or binary, examine the volume browse handler implementation. Look for usages of sh -c with string concatenation involving the path query parameter, which indicates the vulnerable pattern.
    Affected if The code uses sh -c with unsanitized path parameter input in a shell command.

You are affected if your installed Arcane version is 1.18.1 or earlier AND the volume browse endpoint is accessible to authenticated users without additional sanitization of shell metacharacters in the path parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper shell metacharacter escaping or use exec.Command with separate arguments instead of shell execution to prevent command injection in the path parameter.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45626 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data