← Back
CVE-2026-25705
high
CVSS 8.4
Vulnerability in github.com/rancher/rancher (CVE-2026-25705)
Summary
vulnerability in github.com/rancher/rancher (CVE-2026-25705). Successful exploitation can lead to full system takeover. Exploitable via ``compressedEndpoint``. Mitigation: upgrade to `2.11.13` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25705** has been found in github.com/rancher/rancher.
Attackers can target a specific entry point like ``compressedEndpoint`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: upgrade github.com/rancher/rancher to **2.11.13** or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2026-25705" on the vendor's site.
CVE-2026-25705 (github.com/rancher/rancher) — CWE-35 / CVSS v3 8.4
Attack vector: remote (network-reachable)
Attack surface: `compressedEndpoint` / `UIPlugin` / `hostPath` / `index.yaml`
Patched: `2.11.13` — apply immediately
Workaround: There is no workaround.
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-35) exists in github.com/rancher/rancher. Attackers reach the vulnerable code path via ``compressedEndpoint`` without authentication.
📍 Affected scope
github.com/rancher/rancher — . Attack surface: `compressedEndpoint` / `UIPlugin` / `hostPath` / `index.yaml`.
🔥 Severity
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.11.13**.
🛡️ Workaround
Workaround: There is no workaround.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is no workaround.パッチが適用されるまでの応急処置として、There is no workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/rancher/rancher to 2.11.13ステージング環境で 2.11.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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":"2.11.13"}]}]