# CVE-2026-42350: Kargo: Open Redirect in UI OIDC Login Flow via redirectTo Query Parameter > Attackers can redirect users to malicious sites during OIDC login via the redirectTo parameter, potentially facilitating phishing attacks. - **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 8 May 2026 - **Updated:** 12 May 2026 - **Also known as:** GHSA-g7gw-m874-7rmf, GO-2026-6301 ## What is CVE-2026-42350? CVE-2026-42350 is a medium-severity vulnerability in akuity kargo, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Kargo manages and automates the promotion of software artifacts. Prior to versions 1.7.10, 1.8.13, 1.9.8, and 1.10.2, Kargo is vulnerable to open redirect in UI OIDC login flow via the redirectTo query parameter. This issue has been patched in versions 1.7.10, 1.8.13, 1.9.8, and 1.10.2. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2026-42350? 9 open source packages ship an affected version, including github.com/akuity/kargo. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/akuity/kargo` | Go | All versions | 1.7.10, 1.8.13, 1.9.8, 1.10.2 | | `github.com/akuity/kargo` | Go | All versions | 1.7.10 | | `github.com/akuity/kargo` | Go | All versions | 1.7.10 | | `github.com/akuity/kargo` | Go | From 1.10.0 | 1.10.2 | | `github.com/akuity/kargo` | Go | From 1.10.0 | 1.10.2 | | `github.com/akuity/kargo` | Go | From 1.8.0 | 1.8.13 | | `github.com/akuity/kargo` | Go | From 1.8.0 | 1.8.13 | | `github.com/akuity/kargo` | Go | From 1.9.0 | 1.9.8 | | `github.com/akuity/kargo` | Go | From 1.9.0 | 1.9.8 | ## How do I fix CVE-2026-42350? Upgrade github.com/akuity/kargo to a fixed version for your release line: 1.7.10, 1.8.13, 1.9.8 or 1.10.2. ## Is CVE-2026-42350 being exploited? There is no known exploitation of CVE-2026-42350 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-42350 and fix it if it is affected. What it is: CVE-2026-42350 is a medium-severity vulnerability in akuity kargo, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-42350 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/akuity/kargo (Go): affected all versions; fixed in 1.7.10, 1.8.13, 1.9.8, 1.10.2 - github.com/akuity/kargo (Go): affected all versions; fixed in 1.7.10 - github.com/akuity/kargo (Go): affected all versions; fixed in 1.7.10 - github.com/akuity/kargo (Go): affected from 1.10.0; fixed in 1.10.2 - github.com/akuity/kargo (Go): affected from 1.10.0; fixed in 1.10.2 - github.com/akuity/kargo (Go): affected from 1.8.0; fixed in 1.8.13 - github.com/akuity/kargo (Go): affected from 1.8.0; fixed in 1.8.13 - github.com/akuity/kargo (Go): affected from 1.9.0; fixed in 1.9.8 - github.com/akuity/kargo (Go): affected from 1.9.0; fixed in 1.9.8 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-42350/ (Markdown: https://insights.sbomify.com/CVE-2026-42350/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42350 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42350 - OSV: https://osv.dev/vulnerability/CVE-2026-42350 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-42350/ Summaries are generated and may contain mistakes; the official description above is the record.