Is CVE-2026-96626 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-96626 being exploited in the wild.

How severe is CVE-2026-96626?

High severity, with a CVSS score of 8.5, published 16 October 2026.

Which products and versions are affected?

Getarcaneapp Arcane before 2.5.0.

Is there a fix for CVE-2026-96626?

Yes: fixed in 2.5.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-96626 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-96626?

Check whether you run Getarcaneapp Arcane at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-96626: Arcane credential leakage via registry URL change

CVE-2026-96626 · Severity: high · CVSS 8.5 · Published 2026-10-16

Arcane is a container management interface that stores credentials for accessing container registries. A vulnerability allows users with registry management permissions to redirect stored authentication tokens to attacker-controlled hosts by changing the registry URL without providing new credentials. This exposes stored registry passwords or personal access tokens, potentially enabling unauthorized image access or tampering.

Vendors: Getarcaneapp.

Quick answers

Is CVE-2026-96626 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-96626 being exploited in the wild.
How severe is CVE-2026-96626?: High severity, with a CVSS score of 8.5, published 16 October 2026.
Which products and versions are affected?: Getarcaneapp Arcane before 2.5.0.
Is there a fix for CVE-2026-96626?: Yes: fixed in 2.5.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-96626 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-96626?: Check whether you run Getarcaneapp Arcane at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.5.0

Technical details

The vulnerability exists in the UpdateRegistry and TestRegistry functions in container_registry_service.go. When a registry URL is changed without supplying a replacement token, the application reuses the stored encrypted credential and sends it to the attacker-specified destination because URL validation is insufficient. An authenticated attacker with registries:update and registries:test permissions can exploit this via network access to Arcane's API.

Affected products

getarcaneapp Arcane before 2.5.0

Timeline

2026-10-16: disclosed
2026-07-19: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.