dbcve.org
ArcaneApplication

CVE-2026-23944

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-19
Fix available
A fix is available. Upgrade to 1.13.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.13.2, unauthenticated requests could be proxied to remote environment agents, allowing access to remote environment resources without authentication. The environment proxy middleware handled `/api/environments/{id}/...` requests for remote environments before authentication was enforced. When the environment ID was not local, the middleware proxied the request and attached the manager-held agent token, even if the caller was unauthenticated. This enabled unauthenticated access to remote environment operations (e.g., listing containers, streaming logs, or other agent endpoints). An unauthenticated attacker could access and manipulate remote environment resources via the proxy, potentially leading to data exposure, unauthorized changes, or service disruption. Version 1.13.2 patches the vulnerability.

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

Arcane before 1.13.2 has an authentication bypass in its environment proxy middleware. When processing `/api/environments/{id}/...` requests, the middleware proxies requests to remote environments and attaches the manager-held agent token BEFORE authentication is verified. If the environment ID is not local, unauthenticated attackers can access remote environment operations (container listing, log streaming, agent endpoints) by leveraging this proxy behavior.

MitigationUpgrade Arcane to version 1.13.2 or later to patch the authentication bypass. If immediate upgrade is not possible, consider restricting network access to the management interface or implementing additional authentication layers at the network level.

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.13.2

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
High
Availability
High

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

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. Check Arcane version
    Run the command to retrieve the installed Arcane version (e.g., arcane --version, arcane -v, or check the package manager). Compare the version number to the affected range: versions before 1.13.2 are vulnerable.
    Affected if The installed version is less than 1.13.2
  2. Identify configured remote environments
    Examine Arcane's configuration or database to list all environments registered in the system. Determine which environment IDs refer to remote/external environments versus local environments. This can typically be found in the environments configuration file, database, or via an API call if you have admin access.
    Affected if There exists at least one environment with an ID that points to a remote environment (non-local)
  3. Verify API endpoint exposure
    Check if the `/api/environments/{id}/...` endpoint is accessible from the network without authentication. Attempt a curl or similar request to this endpoint with a known remote environment ID and observe if the request is processed (proxied) without being rejected for missing authentication.
    Affected if The API accepts requests to `/api/environments/{remote_id}/...` without requiring valid authentication tokens

You are affected if running Arcane version below 1.13.2 AND your system has remote environments configured AND the environment proxy API endpoint is network-accessible without authentication.

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.13.2 or later
Fixed in 1.13.2
Vendor patch github.com →
Interim mitigation

Upgrade Arcane to version 1.13.2 or later to patch the authentication bypass. If immediate upgrade is not possible, consider restricting network access to the management interface or implementing additional authentication layers at the network level.

Recommended fix High confidence

1.13.2

  1. Backup any existing Arcane data and configuration files
  2. Stop the currently running Arcane container or service
  3. Pull the updated Arcane image or package for version 1.13.2
  4. Deploy version 1.13.2 using the same configuration methodology as the previous installation
  5. Start the upgraded Arcane service
  6. Verify the installation by checking the version number and testing the `/api/environments/{id}/...` endpoint with an unauthenticated request (it should now reject unauthenticated requests)

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

Fix this in Arcane Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23944 — 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-23944 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