Kargo exposes the GetConfig() API endpoint without proper authentication checks, allowing any user who provides a non‑empty Bearer token to retrieve configuration data such as Argo CD cluster endpoints. Adversaries can use this information to enumerate cluster URLs and namespaces, potentially enabling further attacks. The same flaw applies to the RefreshResource endpoint; while it does not reveal data, an unauthenticated attacker could invoke it repeatedly to trigger reconciliations, creating a denial‑of‑service effect by overloading the Kubernetes API server.

Akuity Kargo deployments are vulnerable if they run any version older than 1.8.7, 1.7.7, or 1.6.3. These releases lack the necessary authentication guard on the GetConfig() and RefreshResource APIs. Upgrading to the patched versions removes the flaw.

The vulnerability has a CVSS score of 6.9, indicating moderate severity. The EPSS score is less than 1%, suggesting low current exploitation probability, and the flaw is not listed in the CISA KEV catalog. Exploitation requires only network access to the Kargo API and the provision of any non‑empty Bearer token, meaning the attack vector is external API access and does not require privileged credentials.