Vulnerability in github.com/rancher/fleet (CVE-2026-44937)
Summary
Vulnerability in github.com/rancher/fleet (CVE-2026-44937). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.12.15 or later.
Original description
The description as published by the source.
Potential forgery of webhook requests when using a unauthenticated webhook in SUSE Rancher Fleet 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 and 0.12 before 0.12.5 could be used by remote attackers to cause a denial of service or a downgrade attack on other repositories on the system.
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-44937 has been found in github.com/rancher/fleet.
Risk of unauthorized operations or information disclosure. CVSS score: 8.2/10.
What to do: upgrade github.com/rancher/fleet to 0.12.15 or later.
If unsure, ask your IT team or search "github.com/rancher/fleet CVE-2026-44937" on the vendor's site.
CVE-2026-44937 (github.com/rancher/fleet) — CWE-345 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.12.15 — apply immediately
Workaround: If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret.
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-345) exists in github.com/rancher/fleet.
Check the vendor advisory for the affected versions of github.com/rancher/fleet.
Severity: High (CVSS 8.2/10). Risk of unauthorized operations or information disclosure.
Update to 0.12.15.
Workaround: If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret.パッチが適用されるまでの応急処置として、If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/rancher/fleet to 0.12.15ステージング環境で 0.12.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com