Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-61850— Kargo: Privilege escalation via Project RBAC management in the Kargo API

Quick assessment

Affected
akuity kargo
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Kargo 负责管理和自动化软件制品的发布流程。在版本 0.6.0 至 1.8.14、1.9.9 和 1.10.8 期间， （项目范围的角色基于访问控制 API）中存在两处授权缺陷，使得拥有委托权限以管理某项目中 （角色）或 （服务账户）的已认证用户，能够授予超出其自身权限的访问权。具体而言： 拥有编辑 权限的用户可以创建、替换或添加规则，从而授予其自身并不具备的权限； 拥有编辑某角色所关联 权限的用户，可以将身份（包括其自身身份）绑定到权限更高的角色上。 在 Kargo 中，一个 由项目命名空间内的 、 和 共同

CVSS 9.3 · Critical

Affected Version Matrix 3

VendorProduct Version RangeStatus
akuity kargo >= 0.6.0, < 1.8.14 affected
>= 1.9.0-rc.1, < 1.9.9 affected
>= 1.10.0-rc.1, < 1.10.8 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-61850

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Kargo: Privilege escalation via Project RBAC management in the Kargo API
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
特权管理不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
akuity kargo >= 0.6.0, < 1.8.14 -

II. Public POCs for CVE-2026-61850

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-61850

请登录查看更多情报信息。

Other References for CVE-2026-61850 (9)

IV. Related Vulnerabilities

Same product: kargo
Same vendor: akuity
Same weakness: CWE-269