CVE-2026-44936: SUSE Rancher · Server-Side Request Forgery (SSRF)
Affects SUSE RancherSource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium · fixed in 0.15.2 : update SUSE Rancher when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.15.2, 0.14.6, 0.13.11 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Rancher and Fleet to 0.15.2, 0.14.6, 0.13.11 or 0.12.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SUSERancher | Affected
| Fixed in
|
| SUSERancher | Affected
| Fixed in
|
| SUSERancher | Affected
| Fixed in
|
| SUSERancher | Affected
| Fixed in
|
GitHubFleetpkg:github/FleetOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict push access to fleet monitored git repositories to trusted users only and review helmRepoURLRegex configurations to ensure proper filtering of URLs.
Description
Missing filtering when the helmRepoURLRegex field isn't set on a GitRepo resource in SUSE Rancher Fleet's bundle reader in 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 and 0.12 before 0.12.15 forwards Helm authentication credentials (BasicAuth) to any URL specified in the helm.repo field of a fleet.yaml file, allowing attackers able to push to fleet monitored git repos to leak helm access credentials.