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. Mitigation: upgrade to 0.0.0-20260519172014-d0c047bbc6d2 or later.
Original description
The description as published by the source.
Rancher has over-inclusive team membership expansion in GitHub App authentication provider 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.13.0 before v2.13.6, from v2.14.0 before v2.14.2.
Source: GitHub Security Advisories (Global) 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-41053 has been found in github.com/rancher/rancher.
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
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.
A vulnerability (CWE-303) exists in github.com/rancher/rancher.
Check the vendor advisory for the affected versions of github.com/rancher/rancher.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260519172014-d0c047bbc6d2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade github.com/rancher/rancher to 0.0.0-20260519172014-d0c047bbc6d2ステージング環境で 0.0.0-20260519172014-d0c047bbc6d2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- patch github.com
- patch github.com
- web github.com