dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-47125

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
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. Prior to 1.19.2, the PUT /api/environments/{id}/templates/variables endpoint, which writes the system-wide .env.global file used for variable substitution in every project's compose file, is missing an admin authorization check. Any authenticated non-admin user can call this endpoint with their bearer token or API key and overwrite the global environment variables that are merged into every project deployment. By overriding values like REGISTRY, IMAGE, DATABASE_URL, or SECRET_KEY that other users reference via ${VAR} in compose files, an attacker can redirect image pulls to attacker-controlled registries (supply-chain RCE on the Docker host), exfiltrate database credentials, or disrupt all projects. This vulnerability is fixed in 1.19.2.

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

The PUT /api/environments/{id}/templates/variables endpoint in Arcane prior to 1.19.2 lacks an admin authorization check, allowing any authenticated user to overwrite the system-wide .env.global file used for variable substitution in Docker compose deployments.

MitigationUpgrade Arcane to version 1.19.2 or later to receive the admin authorization fix.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Arcane installation and version
    Locate the Arcane service (e.g., running Docker container, installed binary, or service process) and determine its version from the service banner, container metadata, or version endpoint. Compare against the fixed version 1.19.2.
    Affected if Arcane version is lower than 1.19.2 (e.g., 1.19.1, 1.18.x, or earlier)
  2. Verify API endpoint accessibility
    Confirm the PUT /api/environments/{id}/templates/variables endpoint is reachable in the Arcane deployment. This is typically on the same host/port as the Arcane web interface.
    Affected if The API endpoint is exposed and accessible to authenticated users
  3. Check for non-admin user authentication
    Determine if any user account with basic/standard authentication (non-admin role) exists in the Arcane system. Review user role assignments in the user management or database.
    Affected if At least one non-admin user account is present and able to authenticate to Arcane
  4. Inspect global environment file location
    Locate the .env.global file in the Arcane data directory or compose project directory. This file typically contains shared environment variables (REGISTRY, IMAGE, SECRET_KEY) used across project compose files.
    Affected if A .env.global file exists and is writable by the Arcane service account
  5. Review API authorization configuration
    Examine the Arcane API authorization settings or middleware configuration to verify whether the /api/environments/{id}/templates/variables endpoint enforces admin-only access.
    Affected if The endpoint permits requests from authenticated users without admin role verification

You are affected if Arcane is running with a version lower than 1.19.2, the API endpoint is accessible, and non-admin users can authenticate to modify global environment variables.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Arcane to version 1.19.2 or later to receive the admin authorization fix.

Recommended fix High confidence

1.19.2

  1. Upgrade Arcane to version 1.19.2 or later to remediate this vulnerability.
  2. After upgrading, verify that the PUT /api/environments/{id}/templates/variables endpoint now requires admin authorization.
  3. Review existing .env.global file for any unauthorized changes made prior to the upgrade.
  4. Rotate any credentials that may have been exposed through the global environment variables (e.g., REGISTRY, IMAGE, DATABASE_URL, SECRET_KEY).

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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