Technical impact
The vulnerability in Kargo allows an authenticated user who has been delegated permission to manage a Project's Roles or ServiceAccounts to grant arbitrary permissions beyond their own. By creating or modifying Role rules, the attacker can provide the API server’s privileged credentials to perform operations normally restricted, thereby achieving project‑administrator access, disclosing project secrets, and altering or deleting resources. If the attacker also binds a ServiceAccount to a more powerful Role, they can subvert existing access controls and potentially compromise external systems that rely on stolen credentials. The flaw exists because the API performs a coarse check on the resource kind but does not validate each permission being conferred, enabling escalation when any role‑management delegation exists.
Affected Systems
The flaw affects all versions of Akuity Kargo from the 0.6.0 release up to and including the 1.8.13, 1.9.8, and 1.10.7 releases. It was fixed in the 1.8.14, 1.9.9, and 1.10.8 releases, and therefore any deployment running earlier than those specific patch releases is vulnerable.
Risk and Exploitability
With a CVSS score of 9.3 the vulnerability scores as critical, and it only requires an authenticated user to possess delegated role‑management rights, which are often granted in collaborative environments. No EPSS data is currently available, so exploitation probability cannot be quantified, but the abundance of affected environments and the large impact window raise the likelihood of abuse. The vulnerability is not listed in the CISA KEV catalog, and there is currently no officially documented workaround, so the best defense is patching and tightening RBAC permissions.