dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-42350

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kargo software artifact promotion tool contains an open redirect vulnerability in its UI OIDC login flow. The redirectTo query parameter is not properly validated before redirecting users after authentication, allowing attackers to craft malicious URLs that redirect victims to arbitrary external sites.

MitigationUpgrade to Kargo versions 1.7.10, 1.8.13, 1.9.8, or 1.10.2 and later. If upgrading is not immediately feasible, implement strict allowlist validation on the redirectTo parameter server-side before any redirect occurs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

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/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kargo installation
    Check for Kargo pods or services in your Kubernetes cluster using 'kubectl get pods -A | grep kargo' or 'kubectl get services -A | grep kargo'
    Affected if Kargo is not present in the environment, the vulnerability does not apply
  2. Check installed Kargo version
    Run 'kubectl get deployment -A -l app.kubernetes.io/name=kargo -o jsonpath='{.items[*].spec.template.spec.containers[*].image}' or check your Helm release with 'helm list -A' and 'helm get values <release>'
    Affected if The installed version is before 1.7.10, 1.8.13, 1.9.8, or 1.10.2 (these versions and later contain the fix)
  3. Verify OIDC authentication is enabled
    Examine Kargo configuration for OIDC settings: check for 'oidc' or 'oauth' configurations in Kargo configmaps, CRDs, or environment variables using 'kubectl get configmap -A' or 'kubectl get kargo -A -o yaml'
    Affected if OIDC login is not configured or enabled, the redirectTo vulnerability in the OIDC flow cannot be exploited
  4. Inspect redirect URL handling
    Review Kargo authentication-related code or configuration for how the redirectTo query parameter is processed after OIDC authentication completes
    Affected if No validation logic exists for the redirectTo parameter, allowing arbitrary external URLs to be used as redirect targets

A user is affected if Kargo is running with an unpatched version (below 1.7.10, 1.8.13, 1.9.8, or 1.10.2) and has OIDC authentication enabled with no custom redirectTo validation in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Kargo versions 1.7.10, 1.8.13, 1.9.8, or 1.10.2 and later. If upgrading is not immediately feasible, implement strict allowlist validation on the redirectTo parameter server-side before any redirect occurs.

Recommended fix High confidence

Upgrade to version 1.7.10, 1.8.13, 1.9.8, or 1.10.2 depending on your current release line

  1. 1. Identify the current Kargo version running in your environment
  2. 2. Determine which release line (1.7.x, 1.8.x, 1.9.x, or 1.10.x) you are using
  3. 3. Upgrade to the patched version for your release line: 1.7.10 for 1.7.x, 1.8.13 for 1.8.x, 1.9.8 for 1.9.x, or 1.10.2 for 1.10.x
  4. 4. Verify the upgrade was successful and the Kargo service is running
  5. 5. Test the OIDC login flow with the redirectTo parameter to confirm the open redirect vulnerability is mitigated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data