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