SecOps SignalSecurity Intelligence Workspace
Collection Running31 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2026-96626Public Intelligence Dossier
Source: Source type: NVD · Limited verification•Last verified: •Collection Running
CVE-2026-96626Unknown / EvaluatingHIGH (raw)CVSS 8.5CWE-200

Arcane is an interface for managing Docker containers, images, networks, and volumes

Published: 17 Oct 2026•Last updated: 17 Oct 2026, 03:48 AM IST•Source identifier: security-advisories@github.com
Dossier completeness: source-provided sections 1 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
8.5HIGH (raw)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Metric sourcesecurity-advisories@github.com
EPSS probability
0.2%0.002
Percentile11th
Weakness type
CWE-200
CWE-522
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 2.5.0, UpdateRegistry and TestRegistry in backend/api/services/container_registry_service.go allow the registry URL to change while preserving the stored encrypted token. When a holder of registries:update and registries:test repoints a generic registry URL without supplying a replacement token, TestRegistry decrypts the preserved token and RegistryLogin sends it to the attacker-controlled host because normalizeRegistryServerAddressInternal does not restrict the destination. This exposes the stored container-registry PAT or password and can enable image access or tampering. This issue is fixed in version 2.5.0.

SOC priority

High

Actively exploited

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; No confirmed exploitation signal in current enrichment

Affected Products & Remediation

0 source-backed products
Affected products and versions (source)Not provided by source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched credential-exposure (CWE-522)

Exposure

  1. Identify affected installations and the credential-handling feature described by the source.Telemetry: Application inventory · The CWE alone does not establish which secrets were exposed. · Rule credential-exposure

Exploitation evidence

  1. Review anomalous sign-ins for accounts that could be affected after confirming the exposure path.Telemetry: SigninLogs · Sign-in review is conditional; no compromise is presumed. · Rule credential-exposure

Response

  1. Follow the source mitigation and rotate credentials only where exposure is confirmed or advised.Telemetry: Identity audit logs · Credential response should follow evidence and vendor guidance. · Rule credential-exposure

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
security-advisories@github.com
Record status · verification
UPDATED · NVD API
CPE
Unknown

Evidence & Provenance

3 public sources
nvd.nist.govSource recordgithub.comSource recordgithub.comSource record
Detection Hunting Query

— No published hunting query names this record. Browse community and library queries instead.

Open KQL Library

Correlated briefings

— No published briefing references this CVE

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.