← Back
CVE-2026-41050
critical
CVSS 9.9
Authorization Flaw in github.com/rancher/fleet (CVE-2026-41050)
Summary
vulnerability in github.com/rancher/fleet (CVE-2026-41050). Successful exploitation can lead to full system takeover. Exploitable via ``GitRepo``. Mitigation: upgrade to `0.11.13` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41050** has been found in github.com/rancher/fleet.
Attackers can target a specific entry point like ``GitRepo`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/rancher/fleet to **0.11.13** or later.
If unsure, ask your IT team or search "github.com/rancher/fleet CVE-2026-41050" on the vendor's site.
CVE-2026-41050 (github.com/rancher/fleet) — CWE-863 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `GitRepo` / `lookup` / `valuesFrom` / `fleet.yaml`
Patched: `0.11.13` — 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
**incorrect authorization** (CWE-863) exists in github.com/rancher/fleet. Attackers reach the vulnerable code path via ``GitRepo`` without authentication.
📍 Affected scope
github.com/rancher/fleet — . Attack surface: `GitRepo` / `lookup` / `valuesFrom` / `fleet.yaml`.
🔥 Severity
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.11.13**.
🛡️ 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/rancher/fleet' .` 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/rancher/fleet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/rancher/fleet` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/rancher/fleet to 0.11.13ステージング環境で 0.11.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/rancher/fleet
[{"type":"SEMVER","events":[{"introduced":"0.11.0"},{"fixed":"0.11.13"}]}]