CVE-2026-61850

Kargo: Privilege escalation via Project RBAC management in the Kargo API

Published Oct 30, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
Kargo manages and automates the promotion of software artifacts. From 0.6.0 until 1.8.14, 1.9.9, and 1.10.8, two authorization flaws in the `project-scoped RBAC API` let an authenticated user with delegated permission to manage a Project's `Roles` or `ServiceAccounts` confer permissions exceeding the user's own. A user authorized to edit `Roles` can create, replace, or add rules granting permissions not held by the user; a user authorized to edit a Role's ServiceAccount can bind an identity, including the user's own, to a more powerful Role. A Kargo Role comprises a `ServiceAccount, Role, and RoleBinding` in the Project namespace. Changes are written using the API server's broadly privileged credentials after only a coarse resource-kind edit check, rather than checking each permission being conferred. This permits escalation to Project-administrator access, disclosure of `Project Secrets` and credentials, and modification or deletion of Project resources. Stolen Git, container-registry, or Helm-registry credentials can extend confidentiality and integrity impacts to those external systems. Escalation remains limited to Projects where the attacker already has RBAC-management delegation and does not itself grant cluster-wide or cross-Project access. Default non-administrator roles do not permit these operations; exploitation requires an `administrator-created custom role` granting the relevant permissions and control of an account assigned that role. This issue is fixed in versions 1.8.14, 1.9.9, and 1.10.8.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kargo to version 1.8.14, 1.9.9, 1.10.8, or any later release that contains the fix
  • Verify no custom RBAC roles grant Project‑role or ServiceAccount‑management permissions unless they are strictly necessary
  • Audit and enforce the principle of least privilege by removing or restricting project‑level role and service account editing rights for non‑administrative users

Generated by OpenCVE AI on October 30, 2026 at 20:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Akuity
Akuity kargo
Vendors & Products Akuity
Akuity kargo
Type Values Removed Values Added
Description Kargo manages and automates the promotion of software artifacts. From 0.6.0 until 1.8.14, 1.9.9, and 1.10.8, two authorization flaws in the `project-scoped RBAC API` let an authenticated user with delegated permission to manage a Project's `Roles` or `ServiceAccounts` confer permissions exceeding the user's own. A user authorized to edit `Roles` can create, replace, or add rules granting permissions not held by the user; a user authorized to edit a Role's ServiceAccount can bind an identity, including the user's own, to a more powerful Role. A Kargo Role comprises a `ServiceAccount, Role, and RoleBinding` in the Project namespace. Changes are written using the API server's broadly privileged credentials after only a coarse resource-kind edit check, rather than checking each permission being conferred. This permits escalation to Project-administrator access, disclosure of `Project Secrets` and credentials, and modification or deletion of Project resources. Stolen Git, container-registry, or Helm-registry credentials can extend confidentiality and integrity impacts to those external systems. Escalation remains limited to Projects where the attacker already has RBAC-management delegation and does not itself grant cluster-wide or cross-Project access. Default non-administrator roles do not permit these operations; exploitation requires an `administrator-created custom role` granting the relevant permissions and control of an account assigned that role. This issue is fixed in versions 1.8.14, 1.9.9, and 1.10.8.
Title Kargo: Privilege escalation via Project RBAC management in the Kargo API
Weaknesses CWE-269
References
Metrics cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L'}

Weaknesses
  • CWE-269

    Improper Privilege Management

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 5, 2026, 2:34 AM
Reserved
Jul 10, 2026, 8:28 PM
Status
Deferred
Published
Oct 30, 2026, 8:17 PM
Modified
Nov 5, 2026, 3:17 AM