CVE-2026-24748: Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access

Severity: high (CVSS 7.2 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-01-27 · updated 2026-06-17
Weakness: CWE-863

Description

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.

Affected products

akuity kargo: before 1.6.3; from 1.7.0 before 1.7.7; from 1.8.0 before 1.8.7 — fixed in 1.6.3, 1.7.7, 1.8.7

How to fix

Upgrade to a fixed version: akuity kargo 1.6.3, 1.7.7, 1.8.7. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-24748 or the next vulnerability affects your stack