CVE-2026-27112
YAML Injection in Kargo APIs Enables Privilege Escalation
Publication date: 2026-02-20
Last updated on: 2026-02-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| akuity | kargo | From 1.7.0 (inc) to 1.7.8 (exc) |
| akuity | kargo | From 1.8.0 (inc) to 1.8.11 (exc) |
| akuity | kargo | From 1.9.0 (inc) to 1.9.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Kargo versions from 1.7.0 up to but not including 1.7.8, 1.8.11, and 1.9.3. It affects the batch resource creation endpoints of both Kargo's legacy gRPC API and newer REST API, which accept multi-document YAML payloads.
A specially crafted payload can exploit a bug in the logic of these endpoints to inject arbitrary resources (of specific types only) into the namespace of an existing Project. This injection uses the API server's own permissions, even when such behavior was not intended.
An attacker can leverage this to elevate their own permissions, which can then be used to achieve remote code execution or secret exfiltration. The attacker can also exfiltrate artifact repository credentials, enabling further attacks.
In some Kubernetes cluster configurations underlying the Kargo control plane, these elevated permissions can be used with kubectl to simplify remote code execution or secret exfiltration, though worst-case scenarios remain possible without this.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized elevation of privileges within the Kargo environment.
An attacker exploiting this flaw can execute remote code, potentially taking control of affected systems.
Secret exfiltration is also possible, meaning sensitive information such as artifact repository credentials can be stolen and used for further attacks.
In Kubernetes environments, the attacker may leverage elevated permissions to use kubectl for additional malicious actions, increasing the attack's effectiveness.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Kargo to one of the fixed versions: v1.7.8, v1.8.11, or v1.9.3.