dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-45625

CRITICAL · 9.9 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 →
100/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.0, Arcane's huma-based REST API exposes nine endpoints under /api/customize/git-repositories and /api/git-repositories/sync for managing GitOps source repositories and their stored credentials. Eight of those endpoints (list, create, get, update, delete, test, listBranches, browseFiles) never call the checkAdmin(ctx) helper that every other admin-managed resource (container registries, environments, users, API keys, swarm, settings, system, notifications, events) uses, and the huma authentication middleware deliberately enforces only authentication, not the admin role. As a result, any logged-in user with the default user role can list, create, modify, delete, and test git repository configurations. By repointing an existing repository's URL to an attacker-controlled host while omitting the token/sshKey fields (which UpdateRepository only rewrites when explicitly supplied), the attacker causes Arcane to decrypt the legitimate PAT/SSH key on its next /test, /branches, or /files call and present it as HTTP Basic auth (or SSH key auth) to the attacker's host — producing a one-step exfiltration of plaintext Git credentials. This vulnerability is fixed in 1.19.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

Arcane before 1.19.0 has eight REST API endpoints for managing Git repository configurations that lack admin role verification, allowing any authenticated user to list, create, modify, delete, and test repository settings. An attacker can modify a repository URL to point to an attacker-controlled host and omit credential fields, causing the system to send the legitimate stored PAT/SSH key as authentication to the attacker's server during /test, /branches, or /files calls, resulting in plaintext credential exfiltration.

MitigationUpgrade to Arcane version 1.19.0 or later which implements proper admin role checks on all git-repository endpoints. If immediate upgrade is not possible, audit user permissions and monitor API access logs for unauthorized repository modifications.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 installation directory or container, then check the version file or binary metadata (e.g., look for version info in the binary, package.json, or a VERSION file). Compare the version to the fixed release 1.19.0.
    Affected if The installed version is lower than 1.19.0 and the huma-based REST API is in use.
  2. Verify Git repository endpoints are exposed
    Identify the huma-based REST API endpoints for Git management (typically paths like /api/repos, /git/*, or similar repository management routes). Confirm these eight endpoints exist: list, create, get, update, delete, test, listBranches, browseFiles.
    Affected if Any of these Git repository management endpoints are publicly or internally accessible without additional admin-only restrictions.
  3. Test for missing admin role enforcement
    Using a low-privilege authenticated user account (non-admin), attempt to access or modify each of the eight Git repository endpoints. Send requests to create, update, delete, test, listBranches, or browseFiles and observe if the operations succeed without returning a 403 Forbidden.
    Affected if Non-admin authenticated users can successfully execute create, update, delete, test, listBranches, or browseFiles operations on repositories.
  4. Inspect stored Git credentials configuration
    Examine the Arcane configuration files or database where Git credentials (PAT tokens, SSH keys) are stored. Look for repository configurations that contain URLs and associated credential references.
    Affected if Repository configurations exist with stored PAT/SSH credentials that could be transmitted to a redirected URL.
  5. Check for suspicious repository URL redirections
    Review all stored repository configurations for URLs pointing to unexpected or attacker-controlled hosts. Look for repository URLs where the host differs from your legitimate Git infrastructure.
    Affected if Any repository URL is configured to point to an external or untrusted host, which could be used to exfiltrate credentials during test/branches/files operations.

You are affected if Arcane version is below 1.19.0 and the Git repository management endpoints are accessible to non-admin authenticated users without proper role verification.

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 to Arcane version 1.19.0 or later which implements proper admin role checks on all git-repository endpoints. If immediate upgrade is not possible, audit user permissions and monitor API access logs for unauthorized repository modifications.

Recommended fix High confidence

1.19.0

  1. Identify the currently running Arcane version using the Docker container tag or docker-compose.yml
  2. Stop the existing Arcane container or service
  3. Update the Arcane image or binary to version 1.19.0 or later
  4. For Docker: Update the image tag to 'arcane:1.19.0' or the latest available tag in docker-compose.yml or your container orchestration config
  5. Restart the Arcane service/container
  6. Verify the upgrade was successful by checking the application version
  7. Confirm that the /api/customize/git-repositories and /api/git-repositories/sync endpoints now require admin privileges by attempting access with a non-admin user account (this should be denied)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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