Vulnerability-Lookup

CVE-2026-27111 (GCVE-0-2026-27111)

Vulnerability from cvelistv5 – Published: 2026-02-20 21:17 – Updated: 2026-02-24 18:46

Title

Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints

Summary

Kargo manages and automates the promotion of software artifacts. From v1.9.0 to v1.9.2, Kargo's authorization model includes a promote verb -- a non-standard Kubernetes "dolphin verb" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo's legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, and /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. This vulnerability is fixed in v1.9.3.

Severity ?

5.3 (Medium)


                        
                          CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

CWE

CWE-862 - Missing Authorization

Assigner

GitHub_M

References

URL

Tags

	https://github.com/akuity/kargo/security/advisori…	x_refsource_CONFIRM
	https://github.com/akuity/kargo/commit/833314cad5…	x_refsource_MISC

Impacted products

	Vendor	Product	Version
	akuity	kargo	Affected: >= 1.9.0, < 1.9.3

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-27111",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-02-24T18:44:58.330473Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-02-24T18:46:03.564Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "kargo",
          "vendor": "akuity",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 1.9.0, \u003c 1.9.3"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Kargo manages and automates the promotion of software artifacts. From v1.9.0 to v1.9.2, Kargo\u0027s authorization model includes a promote verb -- a non-standard Kubernetes \"dolphin verb\" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo\u0027s legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, and /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. This vulnerability is fixed in v1.9.3."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "LOW",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "LOW"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862: Missing Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-02-20T21:17:07.383Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4"
        },
        {
          "name": "https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49"
        }
      ],
      "source": {
        "advisory": "GHSA-5vvm-67pj-72g4",
        "discovery": "UNKNOWN"
      },
      "title": "Kargo has Missing Authorization Vulnerabilities in Approval \u0026 Promotion REST API Endpoints"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-27111",
    "datePublished": "2026-02-20T21:17:07.383Z",
    "dateReserved": "2026-02-17T18:42:27.042Z",
    "dateUpdated": "2026-02-24T18:46:03.564Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-27111\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-02-20T22:16:29.187\",\"lastModified\":\"2026-02-25T18:01:51.917\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Kargo manages and automates the promotion of software artifacts. From v1.9.0 to v1.9.2, Kargo\u0027s authorization model includes a promote verb -- a non-standard Kubernetes \\\"dolphin verb\\\" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo\u0027s legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, and /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. This vulnerability is fixed in v1.9.3.\"},{\"lang\":\"es\",\"value\":\"Kargo gestiona y automatiza la promoci\u00f3n de artefactos de software. Desde la v1.9.0 hasta la v1.9.2, el modelo de autorizaci\u00f3n de Kargo incluye un verbo \u0027promote\u0027 -- un \\\"verbo \u0027dolphin\u0027\\\" no est\u00e1ndar de Kubernetes -- que restringe la capacidad de avanzar Freight a trav\u00e9s de una tuber\u00eda de promoci\u00f3n. Este verbo existe para separar la capacidad de gestionar recursos relacionados con la promoci\u00f3n de la capacidad de activar promociones, permitiendo un control de acceso granular sobre lo que a menudo es una operaci\u00f3n sensible. El verbo \u0027promote\u0027 se aplica correctamente en la API gRPC heredada de Kargo. Sin embargo, tres puntos finales en la API REST m\u00e1s reciente omiten esta verificaci\u00f3n, confiando solo en el RBAC est\u00e1ndar de Kubernetes para las operaciones de recursos subyacentes (parche en freights/status o creaci\u00f3n en promotions). Esto permite a los usuarios que poseen esos permisos est\u00e1ndar -- pero a quienes deliberadamente no se les concedi\u00f3 \u0027promote\u0027 -- eludir el l\u00edmite de autorizaci\u00f3n previsto. Los puntos finales afectados son /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, y /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. Esta vulnerabilidad se corrige en la v1.9.3.\"}],\"metrics\":{\"cvssMetricV40\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"4.0\",\"vectorString\":\"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/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\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"attackRequirements\":\"NONE\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"vulnConfidentialityImpact\":\"NONE\",\"vulnIntegrityImpact\":\"LOW\",\"vulnAvailabilityImpact\":\"NONE\",\"subConfidentialityImpact\":\"NONE\",\"subIntegrityImpact\":\"LOW\",\"subAvailabilityImpact\":\"NONE\",\"exploitMaturity\":\"NOT_DEFINED\",\"confidentialityRequirement\":\"NOT_DEFINED\",\"integrityRequirement\":\"NOT_DEFINED\",\"availabilityRequirement\":\"NOT_DEFINED\",\"modifiedAttackVector\":\"NOT_DEFINED\",\"modifiedAttackComplexity\":\"NOT_DEFINED\",\"modifiedAttackRequirements\":\"NOT_DEFINED\",\"modifiedPrivilegesRequired\":\"NOT_DEFINED\",\"modifiedUserInteraction\":\"NOT_DEFINED\",\"modifiedVulnConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedVulnIntegrityImpact\":\"NOT_DEFINED\",\"modifiedVulnAvailabilityImpact\":\"NOT_DEFINED\",\"modifiedSubConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedSubIntegrityImpact\":\"NOT_DEFINED\",\"modifiedSubAvailabilityImpact\":\"NOT_DEFINED\",\"Safety\":\"NOT_DEFINED\",\"Automatable\":\"NOT_DEFINED\",\"Recovery\":\"NOT_DEFINED\",\"valueDensity\":\"NOT_DEFINED\",\"vulnerabilityResponseEffort\":\"NOT_DEFINED\",\"providerUrgency\":\"NOT_DEFINED\"}}],\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N\",\"baseScore\":5.0,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.1,\"impactScore\":1.4}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-862\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:akuity:kargo:*:*:*:*:*:kubernetes:*:*\",\"versionStartIncluding\":\"1.9.0\",\"versionEndExcluding\":\"1.9.3\",\"matchCriteriaId\":\"3B60DE85-B240-4BA0-896D-2A0BA369B0AF\"}]}]}],\"references\":[{\"url\":\"https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Patch\"]},{\"url\":\"https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Vendor Advisory\"]}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-27111\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-02-24T18:44:58.330473Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-02-24T18:45:56.256Z\"}}], \"cna\": {\"title\": \"Kargo has Missing Authorization Vulnerabilities in Approval \u0026 Promotion REST API Endpoints\", \"source\": {\"advisory\": \"GHSA-5vvm-67pj-72g4\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV4_0\": {\"version\": \"4.0\", \"baseScore\": 5.3, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"NONE\", \"privilegesRequired\": \"LOW\", \"subIntegrityImpact\": \"LOW\", \"vulnIntegrityImpact\": \"LOW\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"NONE\", \"subConfidentialityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"NONE\"}}], \"affected\": [{\"vendor\": \"akuity\", \"product\": \"kargo\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 1.9.0, \u003c 1.9.3\"}]}], \"references\": [{\"url\": \"https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4\", \"name\": \"https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49\", \"name\": \"https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"Kargo manages and automates the promotion of software artifacts. From v1.9.0 to v1.9.2, Kargo\u0027s authorization model includes a promote verb -- a non-standard Kubernetes \\\"dolphin verb\\\" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo\u0027s legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, and /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. This vulnerability is fixed in v1.9.3.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-862\", \"description\": \"CWE-862: Missing Authorization\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-02-20T21:17:07.383Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-27111\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-02-24T18:46:03.564Z\", \"dateReserved\": \"2026-02-17T18:42:27.042Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-02-20T21:17:07.383Z\", \"assignerShortName\": \"GitHub_M\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}

FKIE_CVE-2026-27111

Vulnerability from fkie_nvd - Published: 2026-02-20 22:16 - Updated: 2026-02-25 18:01

Severity ?

5.0 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Summary

References

	URL	Tags
	security-advisories@github.com	https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49	Patch
	security-advisories@github.com	https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4	Vendor Advisory

Impacted products

	Vendor	Product	Version
	akuity	kargo	*

JSON

To clipboard

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:akuity:kargo:*:*:*:*:*:kubernetes:*:*",
              "matchCriteriaId": "3B60DE85-B240-4BA0-896D-2A0BA369B0AF",
              "versionEndExcluding": "1.9.3",
              "versionStartIncluding": "1.9.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Kargo manages and automates the promotion of software artifacts. From v1.9.0 to v1.9.2, Kargo\u0027s authorization model includes a promote verb -- a non-standard Kubernetes \"dolphin verb\" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo\u0027s legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, and /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. This vulnerability is fixed in v1.9.3."
    },
    {
      "lang": "es",
      "value": "Kargo gestiona y automatiza la promoci\u00f3n de artefactos de software. Desde la v1.9.0 hasta la v1.9.2, el modelo de autorizaci\u00f3n de Kargo incluye un verbo \u0027promote\u0027 -- un \"verbo \u0027dolphin\u0027\" no est\u00e1ndar de Kubernetes -- que restringe la capacidad de avanzar Freight a trav\u00e9s de una tuber\u00eda de promoci\u00f3n. Este verbo existe para separar la capacidad de gestionar recursos relacionados con la promoci\u00f3n de la capacidad de activar promociones, permitiendo un control de acceso granular sobre lo que a menudo es una operaci\u00f3n sensible. El verbo \u0027promote\u0027 se aplica correctamente en la API gRPC heredada de Kargo. Sin embargo, tres puntos finales en la API REST m\u00e1s reciente omiten esta verificaci\u00f3n, confiando solo en el RBAC est\u00e1ndar de Kubernetes para las operaciones de recursos subyacentes (parche en freights/status o creaci\u00f3n en promotions). Esto permite a los usuarios que poseen esos permisos est\u00e1ndar -- pero a quienes deliberadamente no se les concedi\u00f3 \u0027promote\u0027 -- eludir el l\u00edmite de autorizaci\u00f3n previsto. Los puntos finales afectados son /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, y /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. Esta vulnerabilidad se corrige en la v1.9.3."
    }
  ],
  "id": "CVE-2026-27111",
  "lastModified": "2026-02-25T18:01:51.917",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.0,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.1,
        "impactScore": 1.4,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ],
    "cvssMetricV40": [
      {
        "cvssData": {
          "Automatable": "NOT_DEFINED",
          "Recovery": "NOT_DEFINED",
          "Safety": "NOT_DEFINED",
          "attackComplexity": "LOW",
          "attackRequirements": "NONE",
          "attackVector": "NETWORK",
          "availabilityRequirement": "NOT_DEFINED",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "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": "LOW",
          "providerUrgency": "NOT_DEFINED",
          "subAvailabilityImpact": "NONE",
          "subConfidentialityImpact": "NONE",
          "subIntegrityImpact": "LOW",
          "userInteraction": "NONE",
          "valueDensity": "NOT_DEFINED",
          "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/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": "NONE",
          "vulnConfidentialityImpact": "NONE",
          "vulnIntegrityImpact": "LOW",
          "vulnerabilityResponseEffort": "NOT_DEFINED"
        },
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-02-20T22:16:29.187",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-862"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}

GHSA-5VVM-67PJ-72G4

Vulnerability from github – Published: 2026-02-19 15:16 – Updated: 2026-02-23 22:21

Summary

Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints

Details

Summary

Kargo's authorization model includes a promote verb -- a non-standard Kubernetes "dolphin verb" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation.

The promote verb is correctly enforced in Kargo's legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary.

The affected endpoints are:

POST /v1beta1/projects/{project}/freight/{freight}/approve

Approves Freight for promotion to a specific Stage.

The endpoint is intended to require both patch permission on Freight status and promote permission on the target Stage, but asserts only the former.
POST /v1beta1/projects/{project}/stages/{stage}/promotions

Promotes Freight to a specific Stage.

The endpoint is intended to require both create permission on Promotion resources and promote permission on the target Stage, but asserts only the former.
POST /v1beta1/projects/{project}/stages/{stage}/promotions/downstream

Promotes Freight to all Stages immediately downstream of a given Stage.

The endpoint is intended to require both create permission on Promotion resources and promote permission on each downstream Stage, but asserts only the former.

Base Metrics

The following sections provide the rationale for the values selected for each of CVSS v4's base metrics.

Attack Vector (AV): Network

The affected endpoints are part of Kargo's newer REST API, which is served over HTTP/HTTPS. (The analogous endpoints of the legacy gRPC API correctly check promote permission and are not affected.) No local or physical access is required.

Attack Complexity (AC): Low

The attack requires only well-formed API requests to the affected endpoints.

Attack Requirements (AT): None

No specific environmental conditions are required beyond those that are typical for any Kargo instance.

Privileges Required (PR): Low

The attacker must hold permissions to patch Freight status and/or create Promotion resources. These are standard operational permissions commonly granted to some Kargo users and do not represent what CVSS formally considers administrative or elevated access.

User Interaction (UI): None

The attack is fully automated via API calls. No other user needs to take any action.

Confidentiality Impact to Vulnerable System (VC): None

The vulnerability does not expose any data from the Kargo control plane.

Integrity Impact to Vulnerable System (VI): Low

The attacker can coerce a Stage into a state it might not otherwise transition to. This constitutes bounded state corruption within a single Project. Kargo itself continues to function correctly.

Availability Impact to Vulnerable System (VA): None

Promotion resources created by exploitation of this vulnerability consume the same controller resources as a legitimate Promotion would. A user with proper promote permissions could generate identical load. The vulnerability does not introduce any new avenue for resource exhaustion.

Confidentiality Impact to Subsequent Systems (SC): None

The vulnerability does not provide any mechanism for the attacker to read data from downstream systems.

Integrity Impact to Subsequent Systems (SI): Low

Critically, the attacker does not control the content of Freight resources without artifact repositories also having been compromised. In isolation, which is how vulnerabilities are scored, the worst consequence of a successful attack is downstream systems (e.g. Argo CD) deploying incorrect revisions of artifacts, which in some cases should have been rejected by bypassed segments of the promotion pipeline. Though the operational consequences land on subsequent systems, they are bounded by the attacker's inability to inject arbitrary content.

Availability Impact to Subsequent Systems (SA): None

The attack does not provide any mechanism to degrade the availability of downstream systems beyond what could be achieved with legitimately promoted Freight.

Mitigating Factors

Only the REST API endpoints introduced in v1.9.0 are affected. The legacy gRPC API and the Kargo UI (which uses the gRPC API) correctly enforce the promote permission check and are not vulnerable.
The window of affected versions is narrow: v1.9.0 through v1.9.2.
Exploitation requires authentication to the Kargo API server and specific operational permissions (patch on freights/status or create on promotions). Anonymous or minimally privileged users cannot exploit this vulnerability.
Impact is bounded to a single Project. The promote bypass does not enable cross-Project access or escalation beyond the namespace in which the attacker already holds the prerequisite permissions.
There is no evidence of exploitation in the wild.

Severity ?

5.3 (Medium)


                  
                    CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/akuity/kargo"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.9.0"
            },
            {
              "fixed": "1.9.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-27111"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-02-19T15:16:31Z",
    "nvd_published_at": "2026-02-20T22:16:29Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nKargo\u0027s authorization model includes a `promote` verb -- a non-standard Kubernetes [\"dolphin verb\"](https://www.aquasec.com/blog/kubernetes-verbs/) -- that gates the ability to advance `Freight` through a promotion pipeline. This verb exists to separate the ability to _manage_ promotion-related resources from the ability to _trigger_ promotions, enabling fine-grained access control over what is often a sensitive operation.\n\nThe `promote` verb is correctly enforced in Kargo\u0027s legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (`patch` on `freights/status` or `create` on `promotions`). This permits users who hold those standard permissions -- but who were deliberately _not_ granted `promote` -- to bypass the intended authorization boundary.\n\nThe affected endpoints are:\n\n1. `POST /v1beta1/projects/{project}/freight/{freight}/approve`\n\n    Approves `Freight` for promotion to a specific `Stage`.\n\n    The endpoint is intended to require both `patch` permission on `Freight` status and `promote` permission on the target `Stage`, but asserts only the former.\n\n2. `POST /v1beta1/projects/{project}/stages/{stage}/promotions`\n\n    Promotes `Freight` to a specific `Stage`.\n\n    The endpoint is intended to require both `create` permission on `Promotion` resources and `promote` permission on the target `Stage`, but asserts only the former.\n\n3. `POST /v1beta1/projects/{project}/stages/{stage}/promotions/downstream`\n\n    Promotes `Freight` to all `Stage`s immediately downstream of a given `Stage`.\n\n    The endpoint is intended to require both `create` permission on `Promotion` resources and `promote` permission on each downstream `Stage`, but asserts only the former.\n\n## Base Metrics\n\nThe following sections provide the rationale for the values selected for each of CVSS v4\u0027s base metrics.\n\n### Attack Vector (AV): Network\n\nThe affected endpoints are part of Kargo\u0027s newer REST API, which is served over HTTP/HTTPS. (The analogous endpoints of the legacy gRPC API correctly check `promote` permission and are not affected.) No local or physical access is required.\n\n### Attack Complexity (AC): Low\n\nThe attack requires only well-formed API requests to the affected endpoints.\n\n### Attack Requirements (AT): None\n\nNo specific environmental conditions are required beyond those that are typical for any Kargo instance.\n\n### Privileges Required (PR): Low\n\nThe attacker must hold permissions to patch `Freight` status and/or create `Promotion` resources. These are standard operational permissions commonly granted to some Kargo users and do not represent what CVSS formally considers administrative or elevated access.\n\n### User Interaction (UI): None\n\nThe attack is fully automated via API calls. No other user needs to take any action.\n\n### Confidentiality Impact to Vulnerable System (VC): None\n\nThe vulnerability does not expose any data from the Kargo control plane.\n\n### Integrity Impact to Vulnerable System (VI): Low\n\nThe attacker can coerce a `Stage` into a state it might not otherwise transition to. This constitutes bounded state corruption within a single Project. Kargo itself continues to function correctly.\n\n### Availability Impact to Vulnerable System (VA): None\n\n`Promotion` resources created by exploitation of this vulnerability consume the same controller resources as a legitimate `Promotion` would. A user with proper `promote` permissions could generate identical load. The vulnerability does not introduce any new avenue for resource exhaustion.\n\n### Confidentiality Impact to Subsequent Systems (SC): None\n\nThe vulnerability does not provide any mechanism for the attacker to read data from downstream systems.\n\n### Integrity Impact to Subsequent Systems (SI): Low\n\nCritically, the attacker does not control the _content_ of `Freight` resources without artifact repositories also having been compromised. In isolation, which is how vulnerabilities are scored, the worst consequence of a successful attack is downstream systems (e.g. Argo CD) deploying incorrect revisions of artifacts, which in some cases should have been rejected by bypassed segments of the promotion pipeline. Though the operational consequences land on subsequent systems, they are bounded by the attacker\u0027s inability to inject arbitrary content.\n\n### Availability Impact to Subsequent Systems (SA): None\n\nThe attack does not provide any mechanism to degrade the availability of downstream systems beyond what could be achieved with legitimately promoted `Freight`.\n\n## Mitigating Factors\n\n- Only the REST API endpoints introduced in v1.9.0 are affected. The legacy gRPC API and the Kargo UI (which uses the gRPC API) correctly enforce the `promote` permission check and are not vulnerable.\n\n- The window of affected versions is narrow: v1.9.0 through v1.9.2.\n\n- Exploitation requires authentication to the Kargo API server and specific operational permissions (`patch` on `freights/status` or `create` on `promotions`). Anonymous or minimally privileged users cannot exploit this vulnerability.\n\n- Impact is bounded to a single Project. The `promote` bypass does not enable cross-Project access or escalation beyond the namespace in which the attacker already holds the prerequisite permissions.\n\n- There is no evidence of exploitation in the wild.",
  "id": "GHSA-5vvm-67pj-72g4",
  "modified": "2026-02-23T22:21:12Z",
  "published": "2026-02-19T15:16:31Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27111"
    },
    {
      "type": "WEB",
      "url": "https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/akuity/kargo"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Kargo has Missing Authorization Vulnerabilities in Approval \u0026 Promotion REST API Endpoints"
}

Sightings

Author	Source	Type	Date

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.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2026-27111 (GCVE-0-2026-27111)

FKIE_CVE-2026-27111

GHSA-5VVM-67PJ-72G4

Summary

Base Metrics

Attack Vector (AV): Network

Attack Complexity (AC): Low

Attack Requirements (AT): None

Privileges Required (PR): Low

User Interaction (UI): None

Confidentiality Impact to Vulnerable System (VC): None

Integrity Impact to Vulnerable System (VI): Low

Availability Impact to Vulnerable System (VA): None

Confidentiality Impact to Subsequent Systems (SC): None

Integrity Impact to Subsequent Systems (SI): Low

Availability Impact to Subsequent Systems (SA): None

Mitigating Factors

Tags

Sightings

Nomenclature