CVE-2026-44935 in SUSE Rancher Fleet
Missing validation of "valuesFrom" references in Helm Deployer of 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.15 could be used by owners of one tenant to access fleet credentials of other tenants.
Quick answer
SUSE Rancher Fleet should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Rancher Fleet 0.15.0 before 0.15.2
- Rancher Fleet 0.14.0 before 0.14.6
- Rancher Fleet 0.13.0 before 0.13.11
- Rancher Fleet 0.12.0 before 0.12.15
Fixed versions
- Rancher Fleet 0.15.2 or later
- Rancher Fleet 0.14.6 or later
- Rancher Fleet 0.13.11 or later
- Rancher Fleet 0.12.15 or later
How to fix it
CVE-2026-44935 affects Rancher Fleet. The issue means tenants may read secrets or use resources across namespaces. Treat this as a priority if the system is reachable by users, tenants, or the network. Update to Rancher Fleet 0.15.2, 0.14.6, 0.13.11, or 0.12.15 or later, or follow the vendor advisory if your branch needs a backport.
- Inventory every Rancher Fleet instance, appliance, container, or package in use.
- Compare installed versions with the affected ranges in the vendor advisory.
- Update to Rancher Fleet 0.15.2, 0.14.6, 0.13.11, or 0.12.15 or later on supported systems.
- If you cannot update today, restrict access to trusted admins and trusted networks only.
- Review logs for unusual access, privilege changes, file access, or failed requests.
- Rotate secrets, tokens, and service accounts if exposure or abuse is suspected.
- Document the change and keep the advisory link with the ticket.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is Rancher Fleet 0.15.2, 0.14.6, 0.13.11, or 0.12.15 or later.
- Confirm exposed admin, API, SFTP, or device access is limited to trusted users.
- Retest the affected workflow after the update or mitigation.
- Review logs again after patching for repeated suspicious activity.
- Run a new Fixnx scan where the affected service is part of the public site.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-44935?
SUSE Rancher Fleet versions listed as affected should be reviewed: Rancher Fleet 0.15.0 before 0.15.2, Rancher Fleet 0.14.0 before 0.14.6, Rancher Fleet 0.13.0 before 0.13.11, Rancher Fleet 0.12.0 before 0.12.15.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.