6.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-24748

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

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-24748

CVE-2026-24748:

6.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/akuity/kargo	go	< 1.6.3	1.6.3
github.com/akuity/kargo	go	>= 1.7.0-rc.1, < 1.7.7	1.7.7
github.com/akuity/kargo	go	>= 1.8.0-rc.1, < 1.8.7	1.8.7

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the authentication logic of the Kargo API server. Specifically, the authInterceptor.authenticate function, which is used as a gRPC interceptor to authenticate incoming requests, had a flaw in its token validation process.

Before the patch, the authenticate function had a fallback mechanism. If a provided Authorization header contained a Bearer token that was not a valid JWT, the function would assume it was an opaque token intended for the Kubernetes API server and would pass it through without validation. This is evident from the removed code in the patch.

This behavior was also present for JWTs with an unrecognized issuer.

The GetConfig and RefreshResource API endpoints do not rely on the Kubernetes API server for their operations and thus do not have a subsequent authentication check. As a result, any request to these endpoints with a non-empty Bearer token in the Authorization header was incorrectly treated as authenticated, leading to an authentication bypass.

The patch fixes this vulnerability by removing the permissive fallback logic. Now, if a token is not a valid JWT or is a JWT that cannot be verified by Kargo or the underlying Kubernetes cluster, the authenticate function returns an "invalid token" error, effectively denying access.

Therefore, the authInterceptor.authenticate function is the root of the vulnerability. During exploitation, a profiler would show this function in the call stack for a request to the GetConfig or RefreshResource endpoints.

Vulnerable functions

authInterceptor.authenticate

internal/server/option/auth.go

The `authenticate` function in the `authInterceptor` struct acts as a middleware for authenticating API requests. The vulnerability lies in its handling of non-JWT bearer tokens. The function previously assumed that any non-JWT token was an opaque token for the Kubernetes API server and allowed it to pass without validation. For endpoints like `GetConfig` and `RefreshResource` that do not perform a subsequent authentication check against the Kubernetes API, this resulted in an authentication bypass, allowing any non-empty bearer token.

authInterceptor.authenticate

pkg/server/option/auth.go

This is the same vulnerable function as in `internal/server/option/auth.go`, but at a different path due to code refactoring in different versions of Kargo. The vulnerability and the fix are identical.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.