CVE-2026-27111

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.0
EG Score
5.0(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

February 20, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: github, github_commit.
github Patch Available

Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints · Advisory · akuity/kargo · GitHub

https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4
github_commit

commit 833314cad551 (akuity/kargo)

Fix landed in akuity/kargo commit 833314cad551 — awaiting tagged release

https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/akuity/kargo—1.9.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-18 20:06 UTCOSV refresh
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 19:27 UTCEPSS rescore
  6. 2026-09-17 19:30 UTCEPSS rescore
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-13 16:47 UTCEPSS rescore
  10. 2026-09-12 15:01 UTCEPSS rescore
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-08-30 23:03 UTCOSV refresh
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 35 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:48 UTCEPSS rescore
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 09:20 UTCEG score recompute
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 01:23 UTCEG score recompute
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-11 06:51 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 08:57 UTCEG score recompute
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 21:07 UTCEG score recompute
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-06 03:17 UTCEG score recompute
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-04 15:10 UTCEPSS rescore
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 19:53 UTCEG score recompute
  29. 2026-08-02 02:26 UTCEPSS rescore
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 16:27 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-28 15:36 UTCEPSS rescore
  34. 2026-07-27 14:12 UTCEG score recompute
  35. 2026-07-27 13:55 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27111?
CVE-2026-27111 is a medium vulnerability published on February 20, 2026. 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…
When was CVE-2026-27111 disclosed?
CVE-2026-27111 was first published in the National Vulnerability Database on February 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27111 actively exploited?
CVE-2026-27111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.9% of all scored CVEs.
What is the CVSS score of CVE-2026-27111?
CVE-2026-27111 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-27111?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27111, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27111

Explore →

Is Your Infrastructure Affected by CVE-2026-27111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs