CVE-2026-44936: Github.com/rancher/fleet Rancher Fleet Has SSRF Vulnerability

MODERATE
Advisory Identifier: GHSA-hx4v-cxpf-vh8m
CVSS 5.0
CWE-918
Published
Advisory Summary

CVE-2026-44936 is a MODERATE (CVSS 5.0) rancher fleet has ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Github.com/rancher/fleet libraries in the Go ecosystem. The issue involves rancher fleet has ssrf in bundle reader via unvalidated helm repository url in fleet.yaml. Remediation is available by upgrading affected packages to version 0.15.2, 0.14.6, 0.13.11, 0.12.15.

CVE-2026-44936 at a Glance

CVE Identifier CVE-2026-44936
GHSA Identifier GHSA-hx4v-cxpf-vh8m
Severity MODERATE
CVSS v3.1 Base Score 5.0
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Github.com/rancher/fleet
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.0

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:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-44936

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.

github.com/rancher/fleet fixed: 0.15.2
Upgrade github.com/rancher/fleet to 0.15.2
github.com/rancher/fleet fixed: 0.14.6
Upgrade github.com/rancher/fleet to 0.14.6
github.com/rancher/fleet fixed: 0.13.11
Upgrade github.com/rancher/fleet to 0.13.11
github.com/rancher/fleet fixed: 0.12.15
Upgrade github.com/rancher/fleet to 0.12.15
Verify Direct and Transitive Dependencies

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-44936, 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-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. 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

### Impact A vulnerability has been identified in Fleet when the `helmRepoURLRegex` field isn't set on a `GitRepo` resource. Fleet's bundle reader forwards Helm authentication credentials (`BasicAuth`) to any URL specified in the `helm.repo` field of a `fleet.yaml` file. An attacker with git push access to a Fleet-monitored repository can exploit this behavior by specifying a malicious URL in `helm.repo`. This causes the Fleet controller to send the configured Helm repository credentials to the attacker’s server. As a result, the attacker can capture the username and password that an administrator configured to access a private Helm chart repository. However, the response body from the attacker's server isn't included in the error message (this behavior was fixed in Fleet `v0.13.3` and later), which prevents additional internal data from leaking through the status condition. The final severity of this vulnerability depends on the specific permissions of the leaked credentials. Fleet recommends you to: 1. Review your system for potentially leaked credentials. 2. Replace any credentials that might be compromised. Please consult the associated [MITRE ATT&CK - Technique - Stored Data Manipulation](https://attack.mitre.org/techniques/T1565/001/) and [MITRE ATT&CK - Technique - Steal Application Access Token](https://attack.mitre.org/techniques/T1528/) for further information about this category of attack. ### Patches To resolve this vulnerability, upgrade to a patched version of Fleet. The patched version of Fleet now requires you to set the `helmRepoURLRegex` field on the `GitRepo`. If the `helmRepoURLRegex` is empty or missing, Fleet won’t send credentials, regardless of the URL specified in `fleet.yaml`. When you upgrade, a Helm pre-upgrade job automatically migrates existing `GitRepo` resources that have `helmSecretName` or `helmSecretNameForPaths` configured but lack a `helmRepoURLRegex`. The migration job performs the following actions: The job extracts the scheme and host from the Helm repository URLs already stored in the resource's Bundles. For example, a `GitRepo` with Bundles referencing `https://charts.example.com/stable` receives `helmRepoURLRegex: "^https://charts\.example\.com/"`. This limits credential forwarding to the origins already in use before the upgrade. Migrated resources are annotated with `fleet.cattle.io/helm-regex-auto-migrated: "true"` so you can easily audit them. If no Bundles with Helm repository URLs exist during the migration (for example, if the `GitRepo` has never successfully synced), `helmRepoURLRegex` remains empty and credentials aren't forwarded. You must set this field manually before Fleet will send credentials. The migration job runs only once per installation and records its status in a `ConfigMap` named `fleet-helm-url-regex-migrated` in the Fleet system namespace. Any `GitRepo` resources you create after the upgrade require an explicit `helmRepoURLRegex` to forward credentials. Patched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `0.13.11`, and `v0.12.15`. ### Workarounds If you cannot immediately upgrade to a patched version, use the following methods to mitigate the risk and audit your environment. Set `helmRepoURLRegex` on all `GitRepo` resources that use `helmSecretName`. Ensure the regular expression matches only your legitimate Helm repository URL. Example configuration: ```yaml apiVersion: fleet.cattle.io/v1alpha1 kind: GitRepo metadata: name: my-app namespace: fleet-local spec: repo: https://git.example.com/org/my-app.git helmSecretName: helm-creds helmRepoURLRegex: "^https://charts\\.example\\.com/.*" ``` After upgrading to a patched version, review all auto-migrated `GitRepo` resources by running the following command: ``` kubectl get gitrepo -A -o json | \ jq -r '.items[] | select(.metadata.annotations["fleet.cattle.io/helm-regex-auto-migrated"] == "true") | "\(.metadata.namespace)/\(.metadata.name): \(.spec.helmRepoURLRegex)"' ``` Verify that the auto-derived regular expression matches only your intended Helm repository origins. If a regular expression is broader than necessary, replace it with a more specific pattern. ### Credits This security issue was reported by the following collaborators according to our responsible disclosure policy: - Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC). - FluentLogic's security team. ### References If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - 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/).

CVE-2026-44936 Affected Github.com/rancher/fleet Versions

4 component(s)
Fixed Versions:
0.15.20.14.60.13.110.12.15
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-44936?
CVE-2026-44936 is a security vulnerability in Github.com/rancher/fleet involving Rancher Fleet has SSRF in Bundle Reader via Unvalidated Helm Repository URL in fleet.yaml under CWE-918: Server-Side Request Forgery (SSRF).
Which Github.com/rancher/fleet versions are affected?
Affected versions include releases prior to 0.15.2, 0.14.6, 0.13.11, 0.12.15 across affected packages: github.com/rancher/fleet.
What version fixes CVE-2026-44936?
Upgrading to 0.15.2, 0.14.6, 0.13.11, 0.12.15 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rancher/fleet affected?
Yes, github.com/rancher/fleet is affected in releases prior to 0.15.2, 0.14.6, 0.13.11, 0.12.15. Upgrade your dependency to 0.15.2, 0.14.6, 0.13.11, 0.12.15 or later.
What is the CVSS score of CVE-2026-44936?
CVE-2026-44936 has a CVSS v3.1 base score of 5.0 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2026-44936?
CVE-2026-44936 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Go dependencies for CVE-2026-44936?
Run the dependency tree command: 'inspect dependencies for github.com/rancher/fleet'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hx4v-cxpf-vh8m",
  "modified" : "2026-07-01T20:45:05Z",
  "published" : "2026-07-01T20:45:05Z",
  "aliases" : [ "CVE-2026-44936" ],
  "summary" : "Rancher Fleet has SSRF in Bundle Reader via Unvalidated Helm Repository URL in fleet.yaml",
  "details" : "### Impact\nA vulnerability has been identified in Fleet when the `helmRepoURLRegex` field isn't set on a `GitRepo` resource. Fleet's bundle reader forwards Helm authentication credentials (`BasicAuth`) to any URL specified in the `helm.repo` field of a `fleet.yaml` file.\n\nAn attacker with git push access to a Fleet-monitored repository can exploit this behavior by specifying a malicious URL in `helm.repo`. This causes the Fleet controller to send the configured Helm repository credentials to the attacker’s server. \n\nAs a result, the attacker can capture the username and password that an administrator configured to access a private Helm chart repository. However, the response body from the attacker's server isn't included in the error message (this behavior was fixed in Fleet `v0.13.3` and later), which prevents additional internal data from leaking through the status condition.\n\nThe final severity of this vulnerability depends on the specific permissions of the leaked credentials. \n\nFleet recommends you to:\n1. Review your system for potentially leaked credentials.\n2. Replace any credentials that might be compromised.\n\nPlease consult the associated [MITRE ATT&CK - Technique - Stored Data Manipulation](https://attack.mitre.org/techniques/T1565/001/) and [MITRE ATT&CK - Technique - Steal Application Access Token](https://attack.mitre.org/techniques/T1528/) for further information about this category of attack.\n\n### Patches\nTo resolve this vulnerability, upgrade to a patched version of Fleet. The patched version of Fleet now requires you to set the `helmRepoURLRegex` field on the `GitRepo`. If the `helmRepoURLRegex` is empty or missing, Fleet won’t send credentials, regardless of the URL specified in `fleet.yaml`.\n \nWhen you upgrade, a Helm pre-upgrade job automatically migrates existing `GitRepo` resources that have `helmSecretName` or `helmSecretNameForPaths` configured but lack a `helmRepoURLRegex`. The migration job performs the following actions:\n\nThe job extracts the scheme and host from the Helm repository URLs already stored in the resource's Bundles. For example, a `GitRepo` with Bundles referencing `https://charts.example.com/stable` receives `helmRepoURLRegex: \"^https://charts\\.example\\.com/\"`. This limits credential forwarding to the origins already in use before the upgrade.\nMigrated resources are annotated with `fleet.cattle.io/helm-regex-auto-migrated: \"true\"` so you can easily audit them.\n\nIf no Bundles with Helm repository URLs exist during the migration (for example, if the `GitRepo` has never successfully synced), `helmRepoURLRegex` remains empty and credentials aren't forwarded. You must set this field manually before Fleet will send credentials.\n\nThe migration job runs only once per installation and records its status in a `ConfigMap` named `fleet-helm-url-regex-migrated` in the Fleet system namespace. Any `GitRepo` resources you create after the upgrade require an explicit `helmRepoURLRegex` to forward credentials.\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 cannot immediately upgrade to a patched version, use the following methods to mitigate the risk and audit your environment.\nSet `helmRepoURLRegex` on all `GitRepo` resources that use `helmSecretName`. Ensure the regular expression matches only your legitimate Helm repository URL. \n\nExample configuration:\n```yaml\napiVersion: fleet.cattle.io/v1alpha1\nkind: GitRepo\nmetadata:\n  name: my-app\n  namespace: fleet-local\nspec:\n  repo: https://git.example.com/org/my-app.git\n  helmSecretName: helm-creds\n  helmRepoURLRegex: \"^https://charts\\\\.example\\\\.com/.*\"\n```\n\nAfter upgrading to a patched version, review all auto-migrated `GitRepo` resources by running the following command:\n\n``` \nkubectl get gitrepo -A -o json | \\\n  jq -r '.items[] | select(.metadata.annotations[\"fleet.cattle.io/helm-regex-auto-migrated\"] == \"true\") | \"\\(.metadata.namespace)/\\(.metadata.name): \\(.spec.helmRepoURLRegex)\"'\n```\n\nVerify that the auto-derived regular expression matches only your intended Helm repository origins. If a regular expression is broader than necessary, replace it with a more specific pattern.\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- FluentLogic's security team.\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:L/I:N/A:N"
  } ],
  "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-hx4v-cxpf-vh8m"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rancher/fleet"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-01T20:45:05Z",
    "nvd_published_at" : null
  }
}