← Back
CVE-2026-42350
Open Redirect in github.com/akuity/kargo (CVE-2026-42350)
Summary
vulnerability in github.com/akuity/kargo (CVE-2026-42350). Risk of unauthorized operations or information disclosure. Exploitable via ``redirectTo``. Mitigation: upgrade to `1.10.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42350** has been found in github.com/akuity/kargo.
Attackers can target a specific entry point like ``redirectTo`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/akuity/kargo to **1.10.2** or later.
If unsure, ask your IT team or search "github.com/akuity/kargo CVE-2026-42350" on the vendor's site.
CVE-2026-42350 (github.com/akuity/kargo) — CWE-601 /
Attack surface: `redirectTo`
Patched: `1.10.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-601) exists in github.com/akuity/kargo. Attackers reach the vulnerable code path via ``redirectTo`` without authentication.
📍 Affected scope
github.com/akuity/kargo — . Attack surface: `redirectTo`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.10.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/akuity/kargo' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/akuity/kargo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/akuity/kargo` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/akuity/kargo to 1.10.2ステージング環境で 1.10.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/akuity/kargo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.10.2"}]}]
References
- web https://github.com/akuity/kargo/security/advisories/GHSA-g7gw-m874-7rmf
- web https://nvd.nist.gov/vuln/detail/CVE-2026-42350
- web https://github.com/akuity/kargo/commit/0b89215740e93d18f1ab2187f6f9733137f9d00f
- web https://github.com/akuity/kargo/commit/52107be1d392feaf02d640083cc000be5756f557
- web https://github.com/akuity/kargo/commit/768b2a62dcd70b7b2313290fea6c673e49e0c2d4
- web https://github.com/akuity/kargo/commit/d2c8d185b7cc43e225e0e2d17937511820479834
- web https://github.com/akuity/kargo/commit/db8ca6c015defc5ea29afb32cdea982b657f263a
- web https://github.com/akuity/kargo/releases/tag/v1.10.2
- web https://github.com/akuity/kargo/releases/tag/v1.7.10
- web https://github.com/akuity/kargo/releases/tag/v1.8.13
- web https://github.com/akuity/kargo/releases/tag/v1.9.8
- web https://github.com/advisories/GHSA-g7gw-m874-7rmf