Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access

Summary

Kargo manages and automates the promotion of software artifacts. Prior to versions 1.8.7, 1.7.7, and 1.6.3, a bug was found with authentication checks on the `GetConfig()` API endpoint. This allowed unauthenticated users to access this endpoint by specifying an `Authorization` header with any non-empty `Bearer` token value, regardless of validity. This vulnerability did allow for exfiltration of configuration data such as endpoints for connected Argo CD clusters. This data could allow an attacker to enumerate cluster URLs and namespaces for use in subsequent attacks. Additionally, the same bug affected the `RefreshResource` endpoint. This endpoint does not lead to any information disclosure, but could be used by an unauthenticated attacker to perform a denial-of-service style attack against the Kargo API. `RefreshResource` sets an annotation on specific Kubernetes resources to trigger reconciliations. If run on a constant loop, this could also slow down legitimate requests to the Kubernetes API server. This problem has been patched in Kargo versiosn 1.8.7, 1.7.7, and 1.6.3. There are no workarounds for this issue.

Timeline

1. Jan 27, 2026, 9:23 PM UTCCVE published
2. Jan 28, 2026, 9:15 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Jan 28, 2026, 9:15 PM UTCRecord last updated

Affected versions

• akuity kargo

  fixed in 1.6.3; From 1.7.0 · fixed in 1.7.7; fixed in 1.8.7 · through 1.8.0

• github.com/akuity/kargoGo

  fixed in 1.6.3

• github.com/akuity/kargoGo

  From 1.7.0-rc.1 · fixed in 1.7.7

• github.com/akuity/kargoGo

  From 1.8.0-rc.1 · fixed in 1.8.7

• github.com/akuity/kargoGo

  fixed in 1.6.3; From 1.7.0-rc.1 · fixed in 1.7.7; From 1.8.0-rc.1 · fixed in 1.8.7

References 4