Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2026-27111: 0.21% estimated exploitation activity in the next 30 days; percentile 10.55 (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.

Summary Kargo's authorization model includes a promote verb -- a non-standard Kubernetes "dolphin verb" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo's legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are: 1. POST /v1beta1/projects/{project}/freight/{freight}/approve Approves Freight for promotion to a specific Stage. The endpoint is intended to require both patch permission on…

Published by the source

19 Feb 2026, 15:16 UTC

Last modified by the source

2 Mar 2026, 06:30 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5vvm-67pj-72g4

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

# Patch Next advisory brief: CVE-2026-27111

Advisory: Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints
IDs: CVE-2026-27111, GHSA-5vvm-67pj-72g4
Record: https://patchnext.com/advisories/cve-2026-27111 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
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.9.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/akuity/kargo: affected >= 1.9.0, < 1.9.3; fixed in 1.9.3

## 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-5vvm-67pj-72g4 (GitHub-reviewed advisory GHSA-5vvm-67pj-72g4 lists affected ranges: Go github.com/akuity/kargo >=1.9.0 <1.9.3)

Commands are suggestions: review each one before running it.