Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9

Fleet: Helm impersonation bypass of RESTClientGetter retains cluster-admin during template rendering

CVE-2026-41050GHSA-765j-qfrp-hm3j

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rancher/fleet 0.15.1, 0.14.5, 0.13.10, 0.12.14, 0.11.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/rancher/fleet

    Affected
    >= 0.15.0, < 0.15.1>= 0.14.0, < 0.14.5>= 0.13.0, < 0.13.10>= 0.12.0, < 0.12.14>= 0.11.0, < 0.11.13
    Fixed in
    0.15.1, 0.14.5, 0.12.14, 0.13.10, 0.11.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-41050: 0.39% estimated exploitation activity in the next 30 days; percentile 33.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Fleet's Helm deployer did not fully apply ServiceAccount impersonation in two code paths, allowing a tenant with git push access to a Fleet-monitored repository to read secrets from any namespace on every downstream cluster targeted by their GitRepo. Helm lookup bypass: The Helm template engine ran Kubernetes API queries with the fleet-agent's cluster-admin credentials instead of the impersonated ServiceAccount. A chart template could therefore access resources beyond the tenant's RBAC scope. valuesFrom bypass: Secret and ConfigMap references in fleet.yaml helm.valuesFrom were read using the fleet-agent's cluster-admin client. A tenant could reference resources in namespaces the impersonated ServiceAccount has no access to. Both issues break Fleet's multi-tenant impersonation boundary. The leaked credentials may belong to external services, making the full impact non-deterministic. Single-tenant deployments where all users are trusted are not affected. Important: - For the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-765j-qfrp-hm3j

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41050

Advisory: Fleet: Helm impersonation bypass of `RESTClientGetter` retains `cluster-admin` during template rendering
IDs: CVE-2026-41050, GHSA-765j-qfrp-hm3j
Record: https://patchnext.com/advisories/cve-2026-41050 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rancher/fleet 0.15.1, 0.14.5, 0.13.10, 0.12.14, 0.11.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/fleet: affected >= 0.15.0, < 0.15.1; >= 0.14.0, < 0.14.5; >= 0.13.0, < 0.13.10; >= 0.12.0, < 0.12.14; >= 0.11.0, < 0.11.13; fixed in 0.15.1, 0.14.5, 0.12.14, 0.13.10, 0.11.13

## Suggested inspection (read-only)
- Go github.com/rancher/fleet: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rancher/fleet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-765j-qfrp-hm3j (GitHub-reviewed advisory GHSA-765j-qfrp-hm3j lists affected ranges: Go github.com/rancher/fleet >=0.15.0 =0.14.0 =0.13.0 =0.12.0 =0.11.0 <0.11.13)

Commands are suggestions: review each one before running it.

Loading voting…