CVE-2026-27112: Github.com/akuity/kargo Remote Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-7g9x-cp9g-92mr
CWE-863
Published
Advisory Summary

CVE-2026-27112 is a CRITICAL remote code execution vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/akuity/kargo libraries in the Go ecosystem. The issue involves kargo has an authorization bypass vulnerability in batch resource creation api endpoints. Remediation is available by upgrading affected packages to version 1.9.3, 1.8.11, 1.7.8.

CVE-2026-27112 at a Glance

CVE Identifier CVE-2026-27112
GHSA Identifier GHSA-7g9x-cp9g-92mr
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/akuity/kargo
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-27112

To remediate this vulnerability, upgrade all affected Github.com/akuity/kargo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/akuity/kargo fixed: 1.9.3
Upgrade github.com/akuity/kargo to 1.9.3
github.com/akuity/kargo fixed: 1.8.11
Upgrade github.com/akuity/kargo to 1.8.11
github.com/akuity/kargo fixed: 1.7.8
Upgrade github.com/akuity/kargo to 1.7.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/akuity/kargo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-27112, inspect your project dependencies for Github.com/akuity/kargo:

inspect dependencies for github.com/akuity/kargo

Analyze the terminal output to locate any version of Github.com/akuity/kargo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/akuity/kargo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 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. ## Base Metrics The following sections provide the rationale for the values selected for each of CVSS v4's base metrics. ### Attack Vector (AV): Network The affected endpoints are served by the Kargo API server over HTTP/HTTPS. No local or physical access is required. ### Attack Complexity (AC): Low Exploitation requires only a specially crafted YAML payload sent to an affected API endpoint. ### Attack Requirements (AT): None No specific environmental conditions are required beyond those that are typical for any Kargo instance. ### Privileges Required (PR): Low The attack relies only on the ability to authenticate to the Kargo API server along with basic permissions that are typically granted to all Kargo users. ### User Interaction (UI): None The attack is fully automated via API calls. No other user needs to take any action. ### Confidentiality Impact to Vulnerable System (VC): High Elevated permissions enable secret exfiltration from any Kargo Project. ### Integrity Impact to Vulnerable System (VI): High Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the integrity of the vulnerable system, including Kargo Projects, Kargo control plane components, and the Kargo control plane's underlying Kubernetes cluster. Note: Because it is an integral component of Kargo's control plane, the underlying Kubernetes cluster has been counted as a component of the vulnerable system instead of a subsequent system. ### Availability Impact to Vulnerable System (VA): High Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the availability of the vulnerable system, including Kargo control plane components and the Kargo control plane's underlying Kubernetes cluster. ### Confidentiality Impact to Subsequent Systems (SC): High Secrets exfiltrated from Project namespaces typically contain credentials for external systems. These may enable exfiltration of further confidential information from those systems. ### Integrity Impact to Subsequent Systems (SI): High Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the integrity of subsequent systems. ### Availability Impact to Subsequent Systems (SA): High Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the availability of subsequent systems. ## Mitigating Factors - Exploitation requires authentication to the Kargo API server. Anonymous access is not sufficient. - The most severe consequences of this vulnerability depend on a privilege escalation path (via `RoleBinding` injection) that was not identified by the original reporter, suggesting it is not immediately obvious from the bug alone. - There is no evidence of exploitation in the wild.

CVE-2026-27112 Affected Github.com/akuity/kargo Versions

3 component(s)
Fixed Versions:
1.9.31.8.111.7.8
Product / Package Ecosystem Affected Versions Fixed Version
github.com/akuity/kargo
Go
≥ 1.9.0-rc.1
< 1.9.3
1.9.3
github.com/akuity/kargo
Go
≥ 1.8.0-rc.1
< 1.8.11
1.8.11
github.com/akuity/kargo
Go
≥ 1.7.0
< 1.7.8
1.7.8

References

Frequently Asked Questions

What is CVE-2026-27112?
CVE-2026-27112 is a security vulnerability in Github.com/akuity/kargo involving Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints under CWE-863: Incorrect Authorization.
Which Github.com/akuity/kargo versions are affected?
Affected versions include releases prior to 1.9.3, 1.8.11, 1.7.8 across affected packages: github.com/akuity/kargo.
What version fixes CVE-2026-27112?
Upgrading to 1.9.3, 1.8.11, 1.7.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/akuity/kargo affected?
Yes, github.com/akuity/kargo is affected in releases prior to 1.9.3, 1.8.11, 1.7.8. Upgrade your dependency to 1.9.3, 1.8.11, 1.7.8 or later.
What CWE is associated with CVE-2026-27112?
CVE-2026-27112 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2026-27112?
Run the dependency tree command: 'inspect dependencies for github.com/akuity/kargo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7g9x-cp9g-92mr",
  "modified" : "2026-02-23T22:21:26Z",
  "published" : "2026-02-19T15:16:46Z",
  "aliases" : [ "CVE-2026-27112" ],
  "summary" : "Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints",
  "details" : "## Summary\n\nThe 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.\n\nSpecially 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.\n\nIn 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.\n\n## Base Metrics\n\nThe following sections provide the rationale for the values selected for each of CVSS v4's base metrics.\n\n### Attack Vector (AV): Network\n\nThe affected endpoints are served by the Kargo API server over HTTP/HTTPS. No local or physical access is required.\n\n### Attack Complexity (AC): Low\n\nExploitation requires only a specially crafted YAML payload sent to an affected API endpoint.\n\n### Attack Requirements (AT): None\n\nNo specific environmental conditions are required beyond those that are typical for any Kargo instance.\n\n### Privileges Required (PR): Low\n\nThe attack relies only on the ability to authenticate to the Kargo API server along with basic permissions that are typically granted to all Kargo users.\n\n### User Interaction (UI): None\n\nThe attack is fully automated via API calls. No other user needs to take any action.\n\n### Confidentiality Impact to Vulnerable System (VC): High\n\nElevated permissions enable secret exfiltration from any Kargo Project.\n\n### Integrity Impact to Vulnerable System (VI): High\n\nElevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the integrity of the vulnerable system, including Kargo Projects, Kargo control plane components, and the Kargo control plane's underlying Kubernetes cluster.\n\nNote: Because it is an integral component of Kargo's control plane, the underlying Kubernetes cluster has been counted as a component of the vulnerable system instead of a subsequent system.\n\n### Availability Impact to Vulnerable System (VA): High\n\nElevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the availability of the vulnerable system, including Kargo control plane components and the Kargo control plane's underlying Kubernetes cluster.\n\n### Confidentiality Impact to Subsequent Systems (SC): High\n\nSecrets exfiltrated from Project namespaces typically contain credentials for external systems. These may enable exfiltration of further confidential information from those systems.\n\n### Integrity Impact to Subsequent Systems (SI): High\n\nElevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the integrity of subsequent systems.\n\n### Availability Impact to Subsequent Systems (SA): High\n\nElevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the availability of subsequent systems.\n\n## Mitigating Factors\n\n- Exploitation requires authentication to the Kargo API server. Anonymous access is not sufficient.\n\n- The most severe consequences of this vulnerability depend on a privilege escalation path (via `RoleBinding` injection) that was not identified by the original reporter, suggesting it is not immediately obvious from the bug alone.\n\n- There is no evidence of exploitation in the wild.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/akuity/kargo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.9.0-rc.1"
      }, {
        "fixed" : "1.9.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/akuity/kargo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.8.0-rc.1"
      }, {
        "fixed" : "1.8.11"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/akuity/kargo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.7.0"
      }, {
        "fixed" : "1.7.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/akuity/kargo/security/advisories/GHSA-7g9x-cp9g-92mr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27112"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/akuity/kargo/commit/155c6852ffbffa2902f18e6c7add91a846e8d344"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/akuity/kargo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-19T15:16:46Z",
    "nvd_published_at" : "2026-02-20T22:16:29Z"
  }
}