CVE-2026-27112 Details
Description
Kargo manages and automates the promotion of software artifacts. From 1.7.0 to before v1.7.8, v1.8.11, and v1.9.3, the batch resource creation endpoints of both Kargo's legacy gRPC API and newer REST API accept multi-document YAML payloads. 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 permissions, which can then be leveraged to achieve remote code execution or secret exfiltration. Exfiltrated artifact repository credentials can be leveraged, in turn, to execute further attacks. In some configurations of the Kargo control plane's underlying Kubernetes cluster, elevated permissions may additionally be leveraged to achieve remote code execution or secret exfiltration using kubectl. This can reduce the complexity of the attack, however, worst case scenarios remain entirely achievable even without this. This vulnerability is fixed in v1.7.8, v1.8.11, and v1.9.3.
An authorization bypass vulnerability has been identified in Kargo, a tool for managing and automating software artifact promotion. This vulnerability affects versions 1.7.0 prior to 1.7.8, as well as 1.8.11 and 1.9.3. The issue arises in the batch resource creation endpoints of both Kargo's legacy gRPC API and the newer REST API, which accept multi-document YAML payloads. Exploitation of this vulnerability allows for the injection of arbitrary resources into the namespace of an existing Project, using the API server's permissions. This unintended behavior can be exploited to elevate permissions, potentially leading to remote code execution or unauthorized access to sensitive information. In certain Kargo control plane configurations, the elevated permissions could be used with kubectl to execute further attacks, although the most severe consequences could be achieved without this.
Users can update to Kargo versions 1.7.8, 1.8.11, or 1.9.3 to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 24, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| akuity kargo | >= 1.7.0, < 1.7.8 >= 1.8.0, < 1.8.11 >= 1.9.0, < 1.9.3 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 25, 2026 | Initial Analysis | [email protected] |
| Feb 20, 2026 | New CVE Received | [email protected] |