Skip to main content
Vulnerability Database/CVE-2026-93537

CVE-2026-93537: SUSE Rancher Fleet Information Disclosure

CVE-2026-93537 is an information disclosure vulnerability in SUSE Rancher Fleet that allows attackers to read sensitive files from the filesystem. This post covers technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-93537 Overview

CVE-2026-93537 is a path traversal vulnerability [CWE-23] in SUSE Rancher Fleet affecting bundle processing. A user with write access to a Git repository referenced by a GitRepo resource, or with permission to create or modify a GitRepo, can cause Fleet to read arbitrary files from the filesystem of the environment that processes the bundle. The attacker-controlled bundle then embeds those file contents in the generated Bundle resource. This exposes configuration data and credential material the user has no Kubernetes RBAC permission to read, including Helm registry credentials provided to the bundle-processing job when per-path Helm credentials are configured.

Critical Impact

Attackers with Git push access can exfiltrate Helm registry credentials and other sensitive filesystem content from Fleet bundle-processing environments, bypassing Kubernetes RBAC restrictions.

Affected Products

  • SUSE Rancher Fleet 0.16 before 0.16.2
  • SUSE Rancher Fleet 0.15 before 0.15.7, 0.14 before 0.14.11
  • SUSE Rancher Fleet 0.13 before 0.13.16, 0.12 before 0.12.20

Discovery Timeline

  • 2026-09-28 - CVE-2026-93537 published to NVD
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-93537

Vulnerability Analysis

Fleet processes bundles sourced from Git repositories referenced by GitRepo resources. During processing, Fleet resolves file paths declared inside the bundle and incorporates referenced content into the generated Bundle Kubernetes resource. The processing logic fails to constrain these file paths to the intended bundle directory. An attacker who controls bundle content can specify paths that escape the bundle root and point to arbitrary locations on the processing environment's filesystem.

Because the bundle-processing job runs with access to materials the submitting user cannot read directly, this creates a privilege boundary violation. Per-path Helm registry credentials mounted into the processing job are a primary target. The attacker never needs Kubernetes RBAC permissions on secrets to retrieve their contents.

Root Cause

The root cause is relative path traversal [CWE-23] in the bundle file-resolution logic. Fleet does not canonicalize or validate paths supplied through bundle definitions before reading them from disk. Sequences such as ../ allow references outside the intended working directory, and the resulting file contents are embedded into the generated Bundle resource visible to the submitter.

Attack Vector

Exploitation requires low-privilege authenticated access: Git push rights on a repository referenced by a GitRepo, or Kubernetes permission to create or modify a GitRepo resource. The attacker crafts bundle content containing path references that escape the bundle directory. When Fleet's job processes the bundle, it reads the targeted files and inlines them into the resulting Bundle. The attacker then reads the generated Bundle to retrieve the exfiltrated data. See the GitHub Security Advisory GHSA-wpfm-r97v-3j4h for additional technical context.

Detection Methods for CVE-2026-93537

Indicators of Compromise

  • GitRepo or bundle definitions containing path references with ../ sequences or absolute paths pointing outside the bundle working directory.
  • Generated Bundle resources containing content resembling credentials, environment variables, service account tokens, or Helm registry authentication material.
  • Unexpected commits from low-privilege contributors to repositories referenced by production GitRepo resources.

Detection Strategies

  • Audit all Bundle resources created after Fleet deployment for unexpectedly large payloads or content outside the declared bundle scope.
  • Review Fleet controller and job logs for file-read operations targeting paths outside the expected bundle checkout directory.
  • Correlate Git repository commit history with Fleet bundle generation events to identify suspicious bundle submissions.

Monitoring Recommendations

  • Enable Kubernetes audit logging for create and update operations on GitRepo and Bundle resources in the fleet-* namespaces.
  • Monitor the Fleet bundle-processing job pods for anomalous file access patterns using runtime behavioral telemetry.
  • Alert on any Bundle resource whose content size or structure deviates from established baselines.

How to Mitigate CVE-2026-93537

Immediate Actions Required

  • Upgrade Fleet to a patched release: 0.16.2, 0.15.7, 0.14.11, 0.13.16, or 0.12.20 depending on your deployment branch.
  • Rotate any Helm registry credentials and other secrets that were mounted into Fleet bundle-processing jobs prior to patching.
  • Restrict GitRepo create/modify permissions and Git push access on referenced repositories to trusted principals only.

Patch Information

SUSE has released fixed versions of Rancher Fleet. Upgrade to Fleet 0.16.2, 0.15.7, 0.14.11, 0.13.16, or 0.12.20. Older unsupported versions remain affected and should be migrated to a supported, patched branch. Full remediation details are available in the GitHub Security Advisory GHSA-wpfm-r97v-3j4h.

Workarounds

  • Remove per-path Helm registry credential configurations from the bundle-processing environment until patches are applied.
  • Limit Kubernetes RBAC on GitRepo resources to administrators and tightly control write access to referenced Git repositories.
  • Isolate Fleet bundle-processing jobs so that no sensitive files reside on their filesystem beyond those strictly required.
bash
# Verify the installed Fleet chart version
helm list -n cattle-fleet-system

# Upgrade Fleet to a patched release (example for the 0.16 branch)
helm repo update
helm upgrade fleet rancher/fleet \
  --namespace cattle-fleet-system \
  --version 0.16.2

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.