Kargo
CVE-2026-27112
CRITICAL
GHSA-7g9x-cp9g-92mr
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
DeliverySubmit crafted multi-document YAML payload
-
ExploitInject arbitrary resources into Project namespace
-
ExecutionEscalate permissions via injected resources
-
ImpactExecute commands with elevated privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Kargo versions 1.7.0 to 1.7.7, 1.8.0 to 1.8.10, or 1.9.0 to 1.9.2 with batch resource creation endpoints (gRPC or REST API) enabled. Attacker requires valid authenticated credentials (any user account) and ability to access Kargo API endpoints. No special configuration required beyond default deployment. |
| Impact | CVSS 9.9. Kargo manages software promotions across Kubernetes environments. |
| Exploit ScenarioDerived | Attacker bypasses authorization to create resources in production environments. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 12, 2026
Authorization bypass in Kargo Kubernetes promotion tool from 1.7.0 before 1.7.8/1.8.11/1.9.3. Batch resource creation bypasses authorization checks. Patch available.
Earlier versions of this analysis (1)
Auth bypass in Kargo Kubernetes CD tool.
RemediationAI
Update Kargo.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in go
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-863 in batch resource creation endpoint.
Know when Kargo gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
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.
Executive ViewAI
Kargo artifact promotion systems running versions 1.7.0 through 1.7.7, 1.8.0-1.8.10, and 1.9.0-1.9.2 are vulnerable to critical exploitation via malicious YAML payloads in batch resource creation endpoints. This vulnerability could allow unauthorized attackers to compromise software deployment pipelines, potentially injecting malicious code into production artifacts affecting all downstream systems and customers.
Apply vendor patch. If immediate patching is not feasible: (1) Restrict network access to Kargo batch resource creation endpoints using firewall/network segmentation to trusted CI/CD systems only; (2) Implement WAF rules to reject multi-document YAML payloads in API requests; (3) Disable batch resource creation endpoints if not operationally required; (4) Enable comprehensive API request logging and monitoring for anomalous YAML structures; (5) Enforce strict input validation on all YAML submissions.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)GitHub Advisory
Kargo's GetConfig() API endpoint fails to validate Bearer token authenticity, allowing unauthenticated attackers to retr
Open redirect vulnerability in Kargo UI OIDC login flow allows unauthenticated remote attackers to redirect users to arb
Kargo versions 1.4.0-1.6.3, 1.7.0-1.7.8, 1.8.0-1.8.11, and 1.9.0-1.9.4 contain a Server-Side Request Forgery vulnerabili
Kargo versions 1.9.0 through 1.9.2 fail to enforce the custom "promote" authorization verb in three REST API endpoints,
Same weakness CWE-863 – Incorrect Authorization
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 15.6 | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Fixed |
| openSUSE Leap 15.5 | Fixed |
Exploit-DB