Vulnerability in github.com/rancher/rancher (CVE-2026-41052)
Summary
Vulnerability in github.com/rancher/rancher (CVE-2026-41052). Successful exploitation can lead to full system takeover. Exploitable via privileged. Mitigation: upgrade to 0.0.0-20260513182521-2800aaac25b5 or later.
Original description
The description as published by the source.
Rancher has Privilege Escalation from Project Owner to Host in github.com/rancher/rancher.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/rancher/rancher from v2.12.0 before v2.12.10, from v2.13.0 before v2.13.6, from v2.14.0 before v2.14.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41052 has been found in github.com/rancher/rancher.
Attackers can target a specific entry point like privileged 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-20260513182521-2800aaac25b5 or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2026-41052" on the vendor's site.
CVE-2026-41052 (github.com/rancher/rancher) — CWE-305 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: privileged / projects / updatepsa / get
Patched: 0.0.0-20260513182521-2800aaac25b5 — apply immediately
Workaround: administrators should create a custom project role based on the existing Project Owner role, while removing unrestricted wildcard permissions for project resources.
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.
A vulnerability (CWE-305) exists in github.com/rancher/rancher. Attackers reach the vulnerable code path via privileged.
Check the vendor advisory for the affected versions of github.com/rancher/rancher. Attack surface: privileged / projects / updatepsa / get.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260513182521-2800aaac25b5.
Workaround: administrators should create a custom project role based on the existing Project Owner role, while removing unrestricted wildcard permissions for project resources.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
administrators should create a custom project role based on the existing Project Owner role, while removing unrestricted wildcard permissions for project resources.パッチが適用されるまでの応急処置として、administrators should create a custom project role based on the existing Project Owner role, while removing unrestricted wildcard permissions for project resources. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/rancher/rancher to 0.0.0-20260513182521-2800aaac25b5ステージング環境で 0.0.0-20260513182521-2800aaac25b5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com