Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2026-27112: 0.49% estimated exploitation activity in the next 30 days; percentile 42.25 (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 The batch resource creation endpoints of both Kargo's legacy gRPC API and newer REST API accept multi-document YAML payloads. When either endpoint creates a Project resource, creation of subsequent resources from that same payload belonging in that Project's underlying Kubernetes namespace, by design, proceeds using the API server's own permissions. The creator of a new Project automatically becomes its administrator, but those permissions are granted asynchronously by the management controller. The design choice to create the affected resources using the API server's own permissions averts a race and is contextually appropriate. Specially crafted payloads can manifest a bug present in the logic of both endpoints to inject arbitrary resources (of specific types only) into the underlying namespace of an existing Project using the API server's own permissions when that behavior was not intended. Critically, an attacker may exploit this as a vector for elevating their own…

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-7g9x-cp9g-92mr

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

# Patch Next advisory brief: CVE-2026-27112

Advisory: Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints
IDs: CVE-2026-27112, GHSA-7g9x-cp9g-92mr
Record: https://patchnext.com/advisories/cve-2026-27112 (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: Critical (CVSS 9.4)
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, 1.8.11, 1.7.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/akuity/kargo: affected >= 1.9.0-rc.1, < 1.9.3; >= 1.8.0-rc.1, < 1.8.11; >= 1.7.0, < 1.7.8; fixed in 1.8.11, 1.9.3, 1.7.8

## 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-7g9x-cp9g-92mr (GitHub-reviewed advisory GHSA-7g9x-cp9g-92mr lists affected ranges: Go github.com/akuity/kargo >=1.9.0-rc.1 =1.8.0-rc.1 =1.7.0 <1.7.8)

Commands are suggestions: review each one before running it.