Vulnerabilities in pkg:golang/github.com/akuity/kargo
PACKAGECVE-2026-42350 is a LOW kargo has open redirect vulnerability (CWE-601: URL Redirection to Untrusted Site ('Open Redirect')) affecting Github.com/akuity/kargo libraries in the Go ecosystem. The issue involves kargo has open redirect in ui oidc login flow via redirectto query parameter. Remediation is available by upgrading affected packages to version 1.7.10, 1.8.13, 1.9.8, 1.10.2.
pkg:golang/github.com/akuity/kargo
Vulnerability advisories affecting package pkg:golang/github.com/akuity/kargo. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-g7gw-m874-7rmf | CVE-2026-42350 | LOW | Kargo has Open Redirect in UI OIDC Login Flow via redirectTo Query Parameter |
| GHSA-j94x-8wcp-x7hm | CVE-2026-32828 | MODERATE | Kargo Vulnerable to SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration |
| GHSA-7g9x-cp9g-92mr | CVE-2026-27112 | CRITICAL | Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints |
| GHSA-5vvm-67pj-72g4 | CVE-2026-27111 | MODERATE | Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints |
| GHSA-w5wv-wvrp-v5m5 | CVE-2026-24748 | MODERATE | Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access |
CVE-2026-42350 at a Glance
How to Fix CVE-2026-42350
To remediate this vulnerability, upgrade all affected Github.com/akuity/kargo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/akuity/kargo to 1.7.10
Upgrade github.com/akuity/kargo to 1.8.13
Upgrade github.com/akuity/kargo to 1.9.8
Upgrade github.com/akuity/kargo to 1.10.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/akuity/kargo
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-42350, inspect your project dependencies for Github.com/akuity/kargo:
inspect dependencies for github.com/akuity/kargo
Analyze the terminal output to locate any version of Github.com/akuity/kargo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.10), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect'), where the web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. In Github.com/akuity/kargo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-42350 Affected Github.com/akuity/kargo Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/akuity/kargo
|
Go |
< 1.7.10
|
1.7.10
|
|
github.com/akuity/kargo
|
Go |
≥ 1.8.0
< 1.8.13
|
1.8.13
|
|
github.com/akuity/kargo
|
Go |
≥ 1.9.0
< 1.9.8
|
1.9.8
|
|
github.com/akuity/kargo
|
Go |
≥ 1.10.0
< 1.10.2
|
1.10.2
|
References
Frequently Asked Questions
What is CVE-2026-42350?
Which Github.com/akuity/kargo versions are affected?
What version fixes CVE-2026-42350?
Is github.com/akuity/kargo affected?
What CWE is associated with CVE-2026-42350?
How can I check Go dependencies for CVE-2026-42350?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g7gw-m874-7rmf",
"modified" : "2026-08-27T17:17:37Z",
"published" : "2026-08-27T17:17:36Z",
"aliases" : [ "CVE-2026-42350" ],
"summary" : "Kargo has Open Redirect in UI OIDC Login Flow via redirectTo Query Parameter",
"details" : "## Summary\n\nThe Kargo UI reads a `redirectTo` query parameter on the `/login` and `/token-renew` routes and, following a successful OIDC authentication, uses its value as the destination for client-side navigation. The parameter is treated as a path string but is not constrained to targets within the UI's own origin. Protocol-relative values (e.g. `//attacker.example.com`) and values using a backslash prefix (e.g. `/\\attacker.example.com`) are accepted and result in navigation to an external origin.\n\nAn attacker can exploit this by crafting a URL of the form `https://kargo.example.com/login?redirectTo=/token-renew?redirectTo=/\\attacker.example.com` and delivering it to a victim through any channel that permits link sharing. When the victim follows the link and signs in to Kargo, the browser is redirected to the attacker-controlled origin. Because the initial URL resolves to the legitimate Kargo host and the user is genuinely authenticated in the process, the redirect inherits the perceived trust of the user's own Kargo instance.\n\nThe principal risk is that such a redirect can serve as a stepping stone for credentials phishing. The attacker-controlled page can present a UI resembling Kargo or an associated identity provider and solicit credentials from the user. The vulnerability does not, by itself, expose any data from Kargo or permit modification of Kargo resources, and it does not affect authentication when Kargo's built-in admin credentials are used.\n\n## Base Metrics\n\nThe following sections provide the rationale for the values selected for each of CVSS v4's base metrics. The resulting vector is `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N`, which scores 0.0 (None). This reflects a known limitation of CVSS v4: the standard scopes impact to direct consequences of exploitation, and so does not capture vulnerabilities whose operational significance lies in enabling multi-step attacks. The open redirect here fits that pattern — its immediate effect is benign navigation, and any meaningful harm depends on additional attacker-controlled infrastructure and voluntary actions by the victim. Kargo classifies this vulnerability's severity as Low on a qualitative basis, reflecting the real but bounded operational risk that open redirects pose.\n\n### Attack Vector (AV): Network\n\nThe Kargo UI is served by the Kargo API server over HTTP/HTTPS. No local, adjacent network, or physical access is required.\n\n### Attack Complexity (AC): Low\n\nExploitation requires only a crafted URL. No race conditions, non-default configurations, or prior information gathering are required.\n\n### Attack Requirements (AT): None\n\nNo specific environmental conditions are required beyond a Kargo deployment configured for OIDC authentication, which is the expected configuration for any non-development deployment.\n\n### Privileges Required (PR): None\n\nThe attacker does not need to authenticate to Kargo or hold any permissions. The victim's own authentication completes the redirect.\n\n### User Interaction (UI): Active\n\nExploitation requires a victim to follow the crafted link and then complete the OIDC sign-in flow. Absent this interaction, no redirect occurs.\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): None\n\nThe vulnerability does not permit modification of any data or configuration within Kargo.\n\n### Availability Impact to Vulnerable System (VA): None\n\nThe vulnerability does not provide any mechanism for denial of service against Kargo.\n\n### Confidentiality Impact to Subsequent Systems (SC): None\n\nThe direct consequence of exploitation is navigation to an attacker-controlled URL. Any resulting compromise of the victim's credentials or other data requires the attacker to stage a convincing phishing page and the victim to voluntarily submit information to it — neither action is performed by the exploit itself. CVSS v4 scopes impact to direct consequences of exploitation, so the enabled phishing scenario is not reflected here.\n\n### Integrity Impact to Subsequent Systems (SI): None\n\nThe vulnerability does not modify any data on downstream systems. Tampering an attacker might perform using credentials phished via the enabled redirect would be a consequence of a follow-on attack, not of this vulnerability.\n\n### Availability Impact to Subsequent Systems (SA): None\n\nThe vulnerability does not provide any mechanism to degrade the availability of downstream systems.\n\n## Mitigating Factors\n\n- Exploitation is contingent on social engineering. A victim must both follow the crafted link and complete an authentication flow for the redirect to fire.\n\n- The vulnerability does not directly compromise Kargo or expose any Kargo-held data. Impact is limited to enabling an attacker-controlled destination to be reached via a legitimate Kargo URL.\n\n- There is no evidence of exploitation in the wild.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:U"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/akuity/kargo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.7.10"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/akuity/kargo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.8.0"
}, {
"fixed" : "1.8.13"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/akuity/kargo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.9.0"
}, {
"fixed" : "1.9.8"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/akuity/kargo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.10.0"
}, {
"fixed" : "1.10.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/security/advisories/GHSA-g7gw-m874-7rmf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42350"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/commit/0b89215740e93d18f1ab2187f6f9733137f9d00f"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/commit/52107be1d392feaf02d640083cc000be5756f557"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/commit/768b2a62dcd70b7b2313290fea6c673e49e0c2d4"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/commit/d2c8d185b7cc43e225e0e2d17937511820479834"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/commit/db8ca6c015defc5ea29afb32cdea982b657f263a"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/akuity/kargo"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/releases/tag/v1.10.2"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/releases/tag/v1.7.10"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/releases/tag/v1.8.13"
}, {
"type" : "WEB",
"url" : "https://github.com/akuity/kargo/releases/tag/v1.9.8"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-601" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-27T17:17:36Z",
"nvd_published_at" : "2026-05-08T23:16:38Z"
}
}