CVE-2026-45625: Arcane GitOps Credential Flaw

Are You Affected?

CVE-2026-45625 affects Arcane, an interface for managing Docker containers, images, networks, volumes, and GitOps sources. The affected functionality is the REST API used to manage Git repository configurations, including repository testing, branch listing, and file browsing.

The affected endpoints include /api/customize/git-repositories and /api/git-repositories/sync, along with operations for listing, creating, retrieving, updating, deleting, testing, listing branches, and browsing files. The supplied research identifies nine affected REST operations overall. The key question is not whether a user can log in, but whether the user has administrator authorization.

Arcane’s authentication middleware reportedly verifies that a request comes from an authenticated account, but the affected operations do not consistently invoke the project’s checkAdmin(ctx) authorization helper. An authenticated account with the default user role may therefore manage repository configurations intended to be restricted to administrators.

You should treat a deployment as exposed if it runs any Arcane version earlier than 1.19.0 and permits untrusted or unnecessary users to authenticate. Internet exposure increases the risk, but it is not required for impact. A compromised internal account, shared account, or low-privilege application identity may be sufficient.

For broader guidance on securing AI-enabled and automated systems, see our agentic AI security FAQ.

The Fix, If You’re in a Hurry

Upgrade Arcane to 1.19.0 or later. The reported fix adds administrative authorization checks to the GitOps repository endpoints. Before upgrading, confirm the release is compatible with your deployment and check the project’s current release guidance for supported backports or migration requirements.

The exact upgrade command depends on how Arcane is deployed. Do not substitute an unverified package or image name. Use the project’s documented deployment manifest, compose file, Helm configuration, or package workflow, update the Arcane version reference to 1.19.0 or later, and redeploy. For a containerized deployment, the operational pattern is:

# Replace the image reference with the image and registry used by your deployment.
# The version must be 1.19.0 or later.
docker pull <arcane-image>:1.19.0
docker compose up -d

If your environment uses a pinned digest, update the digest through your approved release process rather than relying on a mutable tag. Verify the running version after deployment using the product’s supported version endpoint or administrative interface. Keep a record of the image digest or package version used for change and incident-response purposes.

If immediate patching is impossible, restrict access to the affected GitOps API paths at a trusted reverse proxy or network control point. The paths identified in the research include:

/api/customize/git-repositories
/api/git-repositories/sync

Blocking these paths may disrupt repository-management functions, so test the control against required workflows. Remove unnecessary Arcane accounts, disable or downgrade untrusted users, restrict Arcane to trusted administrative networks, and prevent outbound connections from Arcane to unapproved destinations where practical.

Because the vulnerability can expose stored personal access tokens or SSH keys, rotate secrets when a vulnerable instance was accessible to untrusted authenticated users, repository settings changed unexpectedly, or repository operations contacted unfamiliar hosts. Rotation should include revocation of old credentials, issuance of replacements with least privilege, and validation that automation and GitOps workflows continue to function.

How This Vulnerability Works

The root cause is an authorization failure. Arcane’s affected endpoints check whether a user is authenticated but do not consistently check whether the user has the administrator role. In other administrative areas, Arcane reportedly uses checkAdmin(ctx); the affected GitOps repository operations omit that protection.

A low-privilege authenticated user can consequently retrieve, update, test, or browse configured repositories. The problem is particularly serious because repository configurations contain credentials that Arcane stores for later Git operations.

The reported attack path relies on how repository updates handle credential fields. If an update request changes the repository URL but omits the token and sshKey fields, the existing stored credentials may remain in the configuration. An attacker can then redirect the repository to an attacker-controlled server without replacing the legitimate secret.

A later test, branch-listing, or file-browsing request can cause Arcane to use the retained credential against the new destination. Depending on the credential type and protocol, the secret may be presented as HTTP Basic authentication or through SSH-key authentication. The result is potential exfiltration of a personal access token or private SSH key to infrastructure controlled by the attacker.

This is best understood as two weaknesses working together: missing administrator authorization and unsafe preservation of stored credentials during attacker-controlled redirection. Even if no credential is immediately exposed, unauthorized repository modification can affect GitOps integrity, source provenance, and downstream deployment behavior.

Technical Notes

The affected operation categories reported for the API include:

list repositories
create repository
retrieve repository
update repository
delete repository
test repository
list branches
browse files
sync-related repository operations

The security boundary that should be enforced is administrator authorization, not merely successful login:

authenticated request
        |
        +-- administrator authorization check
                    |
                    +-- repository-management operation

In vulnerable versions, the relevant path reportedly resembles:

authenticated request
        |
        +-- repository-management operation

The supplied research does not provide the exact request body schema, endpoint suffixes for every operation, or a vendor-provided exploit script. Defenders should therefore avoid treating any single guessed payload as authoritative. The reliable indicators are unauthorized repository configuration changes, destination changes, and subsequent outbound Git or HTTP/SSH activity.

Severity, Explained

The assigned CVSS base score is 9.9, Critical. The supplied NVD response does not include the complete vector string, so the precise component values must be confirmed directly in the NVD record or the Arcane security advisory before using them in compliance reports, risk registers, or formal prioritization models.

The high score is consistent with a remotely reachable API vulnerability that requires authentication but may be exploitable by a low-privilege user. The impact is not limited to changing a display setting: the attack can potentially expose credentials used to access source repositories. Those credentials may provide access to private source code, deployment manifests, infrastructure configuration, container definitions, or other secrets committed to repositories.

The vulnerability also creates an integrity risk. An attacker who can modify repository configuration may redirect Arcane’s GitOps interactions to an unintended source. Depending on how the deployment consumes repository content, this could affect synchronization, source validation, or administrative workflows. The exact downstream impact depends on Arcane configuration and the privileges of the stored Git credentials.

Authentication is required, which matters for prioritization. However, the required account is reportedly not an administrator. Organizations should not downgrade the issue simply because it is not unauthenticated. Low-privilege accounts are common targets after phishing, credential reuse, session theft, or compromise of an internal application.

Analyst’s Take: Patch Arcane before spending time on exploit-status debates. The vulnerable path requires authentication, but the affected account may have only the default user role, and repository redirection can place stored tokens or SSH keys in reach of an attacker-controlled host. If patching must wait, restrict the two identified API paths and review repository changes alongside outbound connections.

Is It Being Exploited?

CVE-2026-45625 is not currently listed in the CISA Known Exploited Vulnerabilities catalog. The supplied assessment records on_kev: false, with no CISA date-added or due-date values. CISA’s catalog therefore does not currently confirm exploitation in the wild.

That status does not prove that exploitation has never occurred. It means only that CISA has not included the CVE in KEV at the time of checking. The available research also found no reliable primary-source confirmation of active in-the-wild exploitation.

Public technical details do exist. The NVD description documents a practical attack path involving repository redirection and subsequent use of stored credentials. However, no verified public proof-of-concept repository was identified in the retrieved authoritative references. The appropriate classification is therefore: technical attack path publicly described, public PoC repository not verified, active exploitation unconfirmed.

Organizations should still treat the vulnerability as urgent. Credential exfiltration vulnerabilities can be exploited selectively and may leave limited evidence if an attacker uses a short-lived destination or deletes configuration changes. The absence of a public exploit or KEV listing is not a substitute for access control and patching.