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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:L · score source

EPSS

• CVE-2026-24748: 0.39% estimated exploitation activity in the next 30 days; percentile 33.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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 vulnerability was identified by security researchers, and there are no known reports…

Published by the source

27 Jan 2026, 22:15 UTC

Last modified by the source

29 Jan 2026, 03:43 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w5wv-wvrp-v5m5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24748

Advisory: Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access
IDs: CVE-2026-24748, GHSA-w5wv-wvrp-v5m5
Record: https://patchnext.com/advisories/cve-2026-24748 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/akuity/kargo 1.8.7, 1.7.7, 1.6.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/akuity/kargo: affected < 1.6.3; >= 1.7.0-rc.1, < 1.7.7; >= 1.8.0-rc.1, < 1.8.7; fixed in 1.6.3, 1.7.7, 1.8.7

## Suggested inspection (read-only)
- Go github.com/akuity/kargo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/akuity/kargo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w5wv-wvrp-v5m5 (GitHub-reviewed advisory GHSA-w5wv-wvrp-v5m5 lists affected ranges: Go github.com/akuity/kargo >=0 =1.7.0-rc.1 =1.8.0-rc.1 <1.8.7)

Commands are suggestions: review each one before running it.