LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23944: Arcane allows unauthenticated proxy access to remote environments

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.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Arcane versions before 1.13.2 could let an unauthenticated person use Arcane’s proxy to reach remote Docker environment agents. Because Arcane attached its stored agent token before checking login, an outsider could access remote environment resources. Business impact may include data exposure, unauthorized container changes, or service disruption.

Executive priority

Prioritize remediation for any internet-facing or broadly reachable Arcane instance managing remote Docker environments. The flaw does not require credentials and could affect confidentiality and integrity of managed environments. Patch availability makes this a straightforward high-priority upgrade rather than a wait-and-see issue.

Technical view

CVE-2026-23944 is a CWE-306 missing authentication flaw in getarcaneapp Arcane before 1.13.2. The proxy middleware processed /api/environments/{id}/... for non-local environments before authentication and forwarded requests with the manager-held agent token. The CVSS v4.0 score is 8.0, network exploitable, low complexity, no privileges, no user interaction.

Likely exposure

Arcane deployments below 1.13.2 that manage remote environments are the primary concern. Exposure is higher where the Arcane web/API service is reachable by untrusted users or networks. Local-only deployments or deployments without remote environment agents may have different practical exposure; the provided sources do not fully define those cases.

Exploitation context

The sources describe unauthenticated access to remote environment operations through the proxy, including listing containers, streaming logs, or other agent endpoints. The CVE record marks exploit maturity as unreported, and the issue is not listed as KEV in the provided bundle. Do not assume active exploitation from these sources alone.

Researcher notes

The root issue is authentication order in environment proxy middleware. The patch is associated with PR #1532 and commit 2008e1b93b25d0c4c3fff3af07843766231614eb. Sources do not provide evidence of public exploitation or KEV status. Avoid extrapolating impact beyond Arcane before 1.13.2 and remote environment proxy behavior.

Mitigation direction

  • Upgrade Arcane to version 1.13.2 or later.
  • Review the GitHub advisory and v1.13.2 release notes.
  • Restrict Arcane web/API access to trusted networks until upgraded.
  • Check vendor guidance if immediate upgrade is not possible.
  • Review remote environment activity for unexpected access or changes.

Validation and detection

  • Inventory all Arcane instances and record their versions.
  • Identify instances managing remote environments or agents.
  • Confirm upgraded instances report version 1.13.2 or later.
  • Review access logs for unauthenticated remote-environment API requests.
  • Verify authentication is enforced before remote environment proxying.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23944 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8High
CVSS 4.0 vector shape for CVE-2026-23944Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
getarcaneapparcane< 1.13.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.