dbcve.org
Rancher FleetApplication · Suse

CVE-2026-44935

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-02
Fix available
A fix is available. Upgrade to 0.12.15 / 0.13.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SUSE Rancher Fleet's Helm Deployer fails to validate 'valuesFrom' references, allowing a tenant to access fleet credentials belonging to other tenants through improperly validated Helm value file references. This is a cross-tenant authorization bypass in the multi-tenant Fleet management system.

MitigationUpgrade Rancher Fleet to version 0.15.2, 0.14.6, 0.13.11, or 0.12.15 or later to patch the missing validation of 'valuesFrom' references.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rancher FleetApplication
Affected:>= 0.12.0, < 0.12.15>= 0.13.0, < 0.13.11>= 0.14.0, < 0.14.6>= 0.15.0, < 0.15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Fleet version
    Run `fleetctl version` or check the Fleet controller pod version in the kube-system namespace via `kubectl get pod -n fleet-system -o jsonpath='{.items[*].spec.containers[*].image}'`
    Affected if The installed version falls within >= 0.12.0 < 0.12.15, >= 0.13.0 < 0.13.11, >= 0.14.0 < 0.14.6, or >= 0.15.0 < 0.15.2
  2. Confirm multi-tenant deployment
    Check if multiple GitRepo resources exist across different namespaces or if Fleet workspaces are used to isolate tenants: `kubectl get gitrepo -A` or `kubectl get workspaces`
    Affected if Multiple GitRepo resources exist across different tenant namespaces or multiple workspaces are configured
  3. Inspect valuesFrom usage in GitRepos
    Query for GitRepo resources containing valuesFrom references: `kubectl get gitrepo -A -o json | jq '.items[] | select(.spec.valuesFrom != null) | {name: .metadata.name, namespace: .metadata.namespace, valuesFrom: .spec.valuesFrom}'`
    Affected if Any GitRepo resources have valuesFrom defined, especially if they reference ConfigMaps or Secrets from other namespaces
  4. Check Bundle resources for valuesFrom
    Examine Bundles for valuesFrom configurations: `kubectl get bundle -A -o json | jq '.items[] | select(.spec.helm.valuesFrom != null) | {name: .metadata.name, namespace: .metadata.namespace}'`
    Affected if Bundles contain helm.valuesFrom definitions that pull from ConfigMaps or Secrets
  5. Audit Secrets accessed across namespaces
    Review ConfigMap and Secret references in valuesFrom to see if they belong to namespaces outside the GitRepo or Bundle namespace: `kubectl get gitrepo -A -o jsonpath='{range .items[*]}{.metadata.name}{.metadata.namespace}{.spec.valuesFrom}{end}'`
    Affected if valuesFrom references point to ConfigMaps or Secrets in namespaces different from where the GitRepo or Bundle resides, indicating cross-namespace credential access is possible

You are affected if your Fleet version is within the vulnerable ranges AND you use multi-tenant configuration with valuesFrom references that may access credentials across tenant boundaries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.12.15 / 0.13.11 / 0.14.6 or later
Fixed in 0.12.150.13.110.14.6
Interim mitigation

Upgrade Rancher Fleet to version 0.15.2, 0.14.6, 0.13.11, or 0.12.15 or later to patch the missing validation of 'valuesFrom' references.

Recommended fix High confidence

Upgrade to Rancher Fleet 0.12.15, 0.13.11, 0.14.6, or 0.15.2 or later (choose the branch matching your current minor version)

  1. 1. Identify the current Rancher Fleet version by checking the Helm chart or GitRepo status
  2. 2. Review the Fleet release notes and upgrade considerations at https://github.com/rancher/fleet/releases
  3. 3. For Rancher-managed deployments: upgrade via the Rancher UI or Helm (e.g., `helm upgrade` the fleet-crd and fleet charts)
  4. 4. For direct Kubernetes deployments: update the fleet-controller, fleet-agent, and gitjob manifests to the fixed version
  5. 5. Verify the upgrade completed successfully by checking pod status and fleet-controller version
Caveat Review release notes for any breaking changes between your current version and the target version, especially when crossing minor version boundaries

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rancher Fleet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44935 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44935 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data