Authenticated privilege escalation via failed Project tracking
Published Feb 20, 2026 · Updated Feb 20, 2026
Incorrect authorization in affected Kargo releases allows remote authenticated users to escalate privileges through batch resource APIs. The gRPC and REST handlers record a Project name as newly created even when its creation fails, so later YAML documents target an existing Project namespace with the API server's permissions. Basic Kargo access is sufficient to inject permitted resource types, enabling secret exfiltration or remote code execution.
Summary
What happened
Incorrect authorization in affected Kargo releases allows remote authenticated users to escalate privileges through batch resource APIs. The gRPC and REST handlers record a Project name as newly created even when its creation fails, so later YAML documents target an existing Project namespace with the API server's permissions. Basic Kargo access is sufficient to inject permitted resource types, enabling secret exfiltration or remote code execution.
The record
- CVE
- CVE-2026-27112
- Published
- Feb 20, 2026
- Updated
- Feb 20, 2026
- Vendor
- Akuity
- Product
- Kargo
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 20, 2026CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.7.0, < 1.7.8
- Affected versionversion=>= 1.8.0-rc.1, < 1.8.11
- Affected versionversion=>= 1.9.0-rc.1, < 1.9.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo