Vulnary
← back to the feed
Critical· 9.9official fix available

CVE-2026-45625

Arcane, a tool for managing Docker containers and GitOps repositories, had a critical flaw that let any logged‑in user modify repository settings and steal stored Git credentials in a single request. The bug existed in all releases before 1.19.0 and was fixed in that version.

publishedMay 29, 2026
last modifiedJul 21, 2026
sourcesNVD
severity · cvss
9.9
critical · how bad it is
exploitation · epss
<1%
32th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 20, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Arcane versions earlier than 1.19.0, used by Docker administrators and developers who manage GitOps repositories through its REST API.

02

Real-world impact

An attacker who can log into Arcane can change a repository URL to point to a malicious server and then trigger a test or file request. Arcane will send the stored personal access token or SSH key to the attacker’s server, giving them full access to the target Git repository.

03

Why this severity

The CVSS score of 9.9 reflects that the vulnerability is network‑based, requires only low effort, and allows an attacker with low privileges to gain complete confidentiality, integrity, and availability of the system by exfiltrating credentials.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade Arcane to version 1.19.0 or later.
  2. 02Restart the Arcane service to ensure the new version is running.

NVD-referenced vendor advisory

05

Timeline

  1. May 29, 2026 · May 29, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 21, 2026 · 14d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 21, 2026 · 14d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredLow
User interactionNone needed
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →