Skip to main content
VulnerabilityPublished Updated

CVE-2026-45625: getarcaneapp arcane · Missing Authorization

Affects getarcaneapp arcaneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 1.19.0 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.19.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade arcane and getarcaneapp/arcane to 1.19.0.

Affected software

ProductAffectedFixed in
getarcaneapparcaneAffected
  • <1.19.0
Fixed in
  • 1.19.0
GitHubgetarcaneapp/arcanepkg:github/getarcaneapp/arcaneOther threatsAffected
  • <1.19.0
Fixed in
  • 1.19.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Arcane to version 1.19.0 or later, where this authorization flaw is fixed. Until upgraded, restrict access to the Arcane API to trusted users only and monitor for suspicious repository configuration changes. Patch status is not explicitly confirmed beyond the fixed version; verify with vendor advisories for the latest remediation guidance.

Description

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.

References

Community reviews

Loading reviews…