CVE-2026-61850 (GCVE-0-2026-61850)
Vulnerability from cvelistv5 – Published: 2026-10-30 19:33 – Updated: 2026-10-30 19:33
VLAI
EPSS
VEX
Title
Kargo: Privilege escalation via Project RBAC management in the Kargo API
Summary
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.
Severity
CWE
- CWE-269 - Improper Privilege Management
Assigner
References
9 references
| URL | Tags |
|---|---|
| https://github.com/akuity/kargo/security/advisori… | x_refsource_CONFIRM |
| https://github.com/akuity/kargo/commit/1963967881… | x_refsource_MISC |
| https://github.com/akuity/kargo/commit/50d29c1015… | x_refsource_MISC |
| https://github.com/akuity/kargo/commit/5ab7c4216a… | x_refsource_MISC |
| https://github.com/akuity/kargo/commit/72fadd3600… | x_refsource_MISC |
| https://github.com/akuity/kargo/releases/tag/v1.10.8 | x_refsource_MISC |
| https://github.com/akuity/kargo/releases/tag/v1.1… | x_refsource_MISC |
| https://github.com/akuity/kargo/releases/tag/v1.8.14 | x_refsource_MISC |
| https://github.com/akuity/kargo/releases/tag/v1.9.9 | x_refsource_MISC |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"product": "kargo",
"vendor": "akuity",
"versions": [
{
"status": "affected",
"version": "\u003e= 0.6.0, \u003c 1.8.14"
},
{
"status": "affected",
"version": "\u003e= 1.9.0-rc.1, \u003c 1.9.9"
},
{
"status": "affected",
"version": "\u003e= 1.10.0-rc.1, \u003c 1.10.8"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s `Roles` or `ServiceAccounts` confer permissions exceeding the user\u0027s 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\u0027s ServiceAccount can bind an identity, including the user\u0027s 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\u0027s 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."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 9.3,
"baseSeverity": "CRITICAL",
"privilegesRequired": "HIGH",
"subAvailabilityImpact": "LOW",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-269",
"description": "CWE-269: Improper Privilege Management",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-30T19:33:01.720Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/akuity/kargo/security/advisories/GHSA-wp4p-hr79-q4g8",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/akuity/kargo/security/advisories/GHSA-wp4p-hr79-q4g8"
},
{
"name": "https://github.com/akuity/kargo/commit/19639678811b486bddb014dabb25397771f3941e",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/commit/19639678811b486bddb014dabb25397771f3941e"
},
{
"name": "https://github.com/akuity/kargo/commit/50d29c10153965114f903645c83eadbe7bf58d3f",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/commit/50d29c10153965114f903645c83eadbe7bf58d3f"
},
{
"name": "https://github.com/akuity/kargo/commit/5ab7c4216a4151f55ea8ef9ff3b9f884dd322578",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/commit/5ab7c4216a4151f55ea8ef9ff3b9f884dd322578"
},
{
"name": "https://github.com/akuity/kargo/commit/72fadd3600b35e6dce67042eb686720a48b45fa3",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/commit/72fadd3600b35e6dce67042eb686720a48b45fa3"
},
{
"name": "https://github.com/akuity/kargo/releases/tag/v1.10.8",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/releases/tag/v1.10.8"
},
{
"name": "https://github.com/akuity/kargo/releases/tag/v1.11.0-rc.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/releases/tag/v1.11.0-rc.1"
},
{
"name": "https://github.com/akuity/kargo/releases/tag/v1.8.14",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/releases/tag/v1.8.14"
},
{
"name": "https://github.com/akuity/kargo/releases/tag/v1.9.9",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/akuity/kargo/releases/tag/v1.9.9"
}
],
"source": {
"advisory": "GHSA-wp4p-hr79-q4g8",
"discovery": "UNKNOWN"
},
"title": "Kargo: Privilege escalation via Project RBAC management in the Kargo API"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-61850",
"datePublished": "2026-10-30T19:33:01.720Z",
"dateReserved": "2026-07-10T20:28:17.513Z",
"dateUpdated": "2026-10-30T19:33:01.720Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-61850",
"date": "2026-10-31",
"epss": "0.00359",
"percentile": "0.29712"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "kargo",
"vendor": "akuity",
"versions": [
{
"status": "affected",
"version": "\u003e= 0.6.0, \u003c 1.8.14"
},
{
"status": "affected",
"version": "\u003e= 1.9.0-rc.1, \u003c 1.9.9"
},
{
"status": "affected",
"version": "\u003e= 1.10.0-rc.1, \u003c 1.10.8"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s `Roles` or `ServiceAccounts` confer permissions exceeding the user\u0027s 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\u0027s ServiceAccount can bind an identity, including the user\u0027s 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\u0027s 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."
}
],
"id": "CVE-2026-61850",
"lastModified": "2026-10-30T20:17:11.530",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 9.3,
"baseSeverity": "CRITICAL",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "HIGH",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "LOW",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
},
"published": "2026-10-30T20:17:11.380",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/commit/19639678811b486bddb014dabb25397771f3941e"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/commit/50d29c10153965114f903645c83eadbe7bf58d3f"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/commit/5ab7c4216a4151f55ea8ef9ff3b9f884dd322578"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/commit/72fadd3600b35e6dce67042eb686720a48b45fa3"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/releases/tag/v1.10.8"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/releases/tag/v1.11.0-rc.1"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/releases/tag/v1.8.14"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/releases/tag/v1.9.9"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/akuity/kargo/security/advisories/GHSA-wp4p-hr79-q4g8"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-269"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.