dbcve.org
ArcaneApplication · Getarcane

CVE-2026-42461

HIGH · 7.5 CVSS v3.1 Published 2026-05-09
Fix available
A fix is available. Upgrade to 1.18.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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. Prior to version 1.18.0, four GET endpoints under /api/templates* in Arcane's Huma backend are registered without any Security requirement, allowing any unauthenticated network client to list and read the full Compose YAML and .env content of every custom template stored in the instance. Because Arcane's UI exposes a "Save as Template" flow on the project / swarm-stack creation pages that persists the operator's real env content (database passwords, API keys, etc.) verbatim, this missing authorization is an unauthenticated read of operator secrets in practice — not a theoretical info-disclosure. The frontend explicitly treats /customize/templates/* as an authenticated area (PROTECTED_PREFIXES in frontend/src/lib/utils/redirect.util.ts), and every CRUD operation (POST/PUT/DELETE) on the same paths requires a Bearer/API key, so this is a clear backend authorization gap, not intended public access. This issue has been patched in version 1.18.0.

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

Four GET endpoints under /api/templates* in Arcane Docker management interface prior to v1.18.0 lack authorization checks, allowing unauthenticated network clients to read all custom templates including their Compose YAML and embedded .env files containing real operator secrets (database passwords, API keys).

MitigationUpgrade to Arcane v1.18.0 or apply the patch to add Security requirements to the four /api/templates* GET endpoints.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArcaneApplication
Affected:< 1.18.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 installation and version
    Locate the Arcane Docker management interface in your environment and retrieve its version number (typically via the web UI, container label, or running 'arcane --version' if CLI is available)
    Affected if The installed version is any version prior to 1.18.0
  2. Verify template endpoint accessibility
    Send a GET request to one of the /api/templates* endpoints (such as /api/templates, /api/templates/list, or similar) without providing any authentication credentials
    Affected if The endpoint returns a successful response with template data or file listings without requiring login or an API token
  3. Check for stored .env files
    If the template endpoints are accessible, inspect the returned data for any .env file contents that may contain plaintext secrets such as passwords or API keys
    Affected if The response includes .env files or Compose YAML templates with visible plaintext credentials

You are affected if Arcane version is below 1.18.0 AND the /api/templates endpoints respond to unauthenticated requests, exposing sensitive template or .env file contents.

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.

dbcve · scoped
Upgrade available Upgrade to 1.18.0 or later
Fixed in 1.18.0
Interim mitigation

Upgrade to Arcane v1.18.0 or apply the patch to add Security requirements to the four /api/templates* GET endpoints.

Recommended fix High confidence

Arcane 1.18.0

  1. Upgrade Arcane to version 1.18.0 or later to remediate the missing authorization vulnerability
  2. After upgrading, verify that the GET endpoints under /api/templates* now require authentication (Bearer/API key)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arcane 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 the upgrade done

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-42461 — 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-42461 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