CVE-2026-44938: Github.com/rancher/fleet Fleet Has PSS Bypass Through Vulnerability
HIGHCVE-2026-44938 is a HIGH (CVSS 8.8) fleet has pss bypass through vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Github.com/rancher/fleet libraries in the Go ecosystem. The issue involves fleet has pss bypass through addlabelsfromoptions in fleet agent. Remediation is available by upgrading affected packages to version 0.15.2, 0.14.6, 0.13.11, 0.12.15.
CVE-2026-44938 at a Glance
Security Impact
CVSS: 8.8
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:U/C:H/I:H/A:H).
How to Fix CVE-2026-44938
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-44938, 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-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. 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-44938 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-44938?
Which Github.com/rancher/fleet versions are affected?
What version fixes CVE-2026-44938?
Is github.com/rancher/fleet affected?
What is the CVSS score of CVE-2026-44938?
What CWE is associated with CVE-2026-44938?
How can I check Go dependencies for CVE-2026-44938?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-864g-863m-vcvq",
"modified" : "2026-07-01T20:35:37Z",
"published" : "2026-07-01T20:35:37Z",
"aliases" : [ "CVE-2026-44938" ],
"summary" : "Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent",
"details" : "### Impact\nA vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from `namespaceLabels` in `fleet.yaml` (or `BundleDeployment.spec.options.namespaceLabels`) when applying them to the target namespace. \n\nAn attacker with `git push` access to a Fleet-monitored repository could overwrite Pod Security Standards (PSS) enforcement labels on a target namespace. This allows the attacker to weaken admission controls and deploy workloads that PSS policies would otherwise block.\n\n**Important:** The final impact on confidentiality, integrity, and availability depends on the specific permissions of the leaked credentials. \n\nFleet team recommends you:\n1. Review your system for potentially leaked credentials.\n2. Replace any credentials that may be compromised.\n\nPlease consult the associated [MITRE ATT&CK - Technique - Disable or Modify Tools](https://attack.mitre.org/techniques/T1685/) for further information about this category of attack.\n\n### Patches\nTo fix this issue, upgrade to a patched version. The updated Fleet deployer filters out labels with the `pod-security.kubernetes.io/` prefix when applying `namespaceLabels` to a namespace. This change preserves the PSS labels set by cluster administrators and prevents them from being overwritten through `fleet.yaml` or `BundleDeployment` options.\n\nPatched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `v0.13.11`, and `v0.12.15`.\n\n### Workarounds\nIf you can’t immediately upgrade to a patched version, use one of the following workarounds:\n\n**1 - Deploy NeuVector(primary workaround)**\n\nDeploy NeuVector (SUSE Security) and configure an admission control Deny rule for \"Run as privileged\" in Protect mode. \n- NeuVector evaluates pod specs independently of Kubernetes PSS namespace labels. It blocks privileged containers even if the labels are downgraded. \n- Although the namespace labels are still overwritten, the attack cannot exploit confidentiality, integrity, or availability without a privileged pod.\n\n**2 - Restrict repository access (secondary workaround)**\n\n**Note:** The following measure reduces the attack surface but does not close the vulnerability:\n- In a multi-tenant setup, this restriction removes the primary attack vector. However, this measure only reduces the attack surface and doesn't completely close the vulnerability. It may also not be operationally viable for all organizations. ´\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\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:U/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-864g-863m-vcvq"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/rancher/fleet"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-522" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-01T20:35:37Z",
"nvd_published_at" : null
}
}