CVE-2026-44935: Github.com/rancher/fleet Rancher Fleet Vulnerable To Cross Vulnerability
CRITICALCVE-2026-44935 is a CRITICAL (CVSS 9.9) rancher fleet vulnerable to cross vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/rancher/fleet libraries in the Go ecosystem. The issue involves rancher fleet vulnerable to cross namespace secret disclosure via unvalidated `valuesfrom` references in helm deployer. Remediation is available by upgrading affected packages to version 0.15.2, 0.14.6, 0.13.11, 0.12.15.
CVE-2026-44935 at a Glance
Security Impact
CVSS: 9.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-44935
To remediate this vulnerability, upgrade all affected Github.com/rancher/fleet dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/rancher/fleet to 0.15.2
Upgrade github.com/rancher/fleet to 0.14.6
Upgrade github.com/rancher/fleet to 0.13.11
Upgrade github.com/rancher/fleet to 0.12.15
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/rancher/fleet
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-44935, inspect your project dependencies for Github.com/rancher/fleet:
inspect dependencies for github.com/rancher/fleet
Analyze the terminal output to locate any version of Github.com/rancher/fleet in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.15.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/rancher/fleet, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-44935 Affected Github.com/rancher/fleet Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/rancher/fleet
|
Go |
≥ 0.15.0
< 0.15.2
|
0.15.2
|
|
github.com/rancher/fleet
|
Go |
≥ 0.14.0
< 0.14.6
|
0.14.6
|
|
github.com/rancher/fleet
|
Go |
≥ 0.13.0
< 0.13.11
|
0.13.11
|
|
github.com/rancher/fleet
|
Go |
≥ 0.12.0
< 0.12.15
|
0.12.15
|
References
Frequently Asked Questions
What is CVE-2026-44935?
Which Github.com/rancher/fleet versions are affected?
What version fixes CVE-2026-44935?
Is github.com/rancher/fleet affected?
What is the CVSS score of CVE-2026-44935?
What CWE is associated with CVE-2026-44935?
How can I check Go dependencies for CVE-2026-44935?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-xr65-5cpm-g36x",
"modified" : "2026-07-01T20:45:39Z",
"published" : "2026-07-01T20:45:39Z",
"aliases" : [ "CVE-2026-44935" ],
"summary" : "Rancher Fleet vulnerable to cross namespace secret disclosure via unvalidated `valuesFrom` references in Helm Deployer",
"details" : "### Impact\nA vulnerability in Fleet for Rancher Manager affects multi-tenancy environments where different tenants share the same downstream clusters (e.g., different privileged or untrusted teams inside the same organization). \n\nOn unpatched versions, tenants could bypass restrictions to access any config map or secret across all namespaces on the downstream cluster. They can create cluster-wide resources using `HelmOp` or `Bundle` without authorization.\nSpecifically, an attacker can exploit this vulnerability in the following ways:\n1. Use `valuesFrom` in `fleet.yaml`(through a `GitRepo` resource) or a `HelmOp resource to read the contents of any secret an on the downstream cluster, provided they know or can guess the name, namespace, and key.\n2. Deploy `HelmOp` and `Bundle` resources without being restricted to a specific service account for the Fleet agent.\n\nIf you use Fleet in a multi-tenant environment, it's recommended that you:\n- Review your cluster and Fleet deployments logs for indicators of unauthorized access across tenant namespaces.\n- Rotate any service accounts and credentials that might have been exposed.\n\nPlease consult the associated [MITRE ATT&CK - Technique - Unsecured Credentials](https://attack.mitre.org/techniques/T1552/) for further information about this category of attack.\n\n### Patches\nTo resolve this vulnerability, upgrade to a patched version of Fleet. The new Policy resource allows you to:\n- Configure `GitRepos`, `HelmOps`, and `Bundles` to require a specific service account for the Fleet agent on downstream clusters used for deployment. The agent uses these designated service accounts for operations, blocking access to unauthorized resources.\n- Restrict `HelmOp` repository and chart URLs by using a regular expression. The regular expression is automatically anchored with `^` and `$`, meaning it must match the entire URL string.\n\nLike `GitRepoRestriction`, a Policy resource must be created in the specific namespace you want to restrict, and it only applies to that namespace.\n\n**Note:** Before applying a policy, ensure that the required service account is available on the downstream clusters and is configured with least-privilege permissions.\n\nPatched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `0.13.11`, and `v0.12.15`.\n\n### Workarounds\nIf you can't upgrade to a fixed version, please make sure that tenants do not have shared access to the same downstream clusters.\n\n### Credits\n\nThis security issue was reported by the following collaborators according to our responsible disclosure policy:\n\n- Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC).\n\n### References\nIf you have any questions or comments about this advisory:\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/rancher/fleet"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.15.0"
}, {
"fixed" : "0.15.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/rancher/fleet"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.14.0"
}, {
"fixed" : "0.14.6"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/rancher/fleet"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.13.0"
}, {
"fixed" : "0.13.11"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/rancher/fleet"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.12.0"
}, {
"fixed" : "0.12.15"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/rancher/fleet/security/advisories/GHSA-xr65-5cpm-g36x"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/rancher/fleet"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-863" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-01T20:45:39Z",
"nvd_published_at" : null
}
}