Description
A security vulnerability was discovered in Fleet's Helm template preprocessing where templates evaluated by the Fleet controller could reach network resources outside the management cluster. A user who can supply bundle content to a repository referenced by a `GitRepo` resource can cause the Fleet controller to:
- Disclose cluster metadata available to the templating context.
- Reveal information about hosts reachable from the controller's network position.
Because the disclosure channel is name resolution, it may remain effective in environments where outbound traffic is otherwise restricted. The disclosed information is limited to values exposed to the Fleet templating context and to name resolution results. Integrity and availability of managed clusters are not affected.

This issue affects Fleet:
from 0.12.0 before 0.12.19,
from 0.13.0 before 0.13.15,
from 0.14.0 before 0.14.10,
from 0.15.0 before 0.15.6, and
from 0.16.0 before 0.16.1.
Published: 2026-09-03
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows a user who can supply bundle content to a GitRepo resource to cause the Fleet controller to perform DNS lookups via the Sprig getHostByName function. The lookup exposes cluster metadata and the list of hosts reachable from the controller, yet it does not affect integrity or availability of the managed clusters.

Affected Systems

The flaw was present in fleet controller versions 0.12.0 through 0.12.18, 0.13.0 through 0.13.14, 0.14.0 through 0.14.9, 0.15.0 through 0.15.5, and 0.16.0. The affected product is SUSE Fleet. Upgrading to 0.12.19, 0.13.15, 0.14.10, 0.15.6, or 0.16.1 removes the flaw.

Risk and Exploitability

With a CVSS base score of 5.3 the vulnerability is moderate. EPSS is not available and the flaw is not listed in the CISA KEV catalog. An attacker must have permission to add or modify bundle content for a GitRepo resource, a privilege generally given to cluster administrators or CI/CD pipelines, to trigger the exploit. The attack vector involves the Fleet controller performing external DNS queries, which can be effective even when outbound traffic is otherwise restricted, so the risk exists in tightly‑controlled environments. The lack of integrity or availability impact does not lower the threat level, as the exposed metadata can aid discovery or lateral movement.

Generated by OpenCVE AI on September 3, 2026 at 16:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Fleet to at least 0.12.19 or newer releases that contain the patch.
  • If an immediate upgrade is impossible, restrict who can create or modify GitRepo resources to trusted users and enforce least‑privilege permissions on repository write access.
  • As a temporary workaround, disable or remove usage of the Sprig getHostByName function in fleet.yaml templates and ensure templates do not perform external name resolution.
  • Monitor for unexpected DNS lookups from the Fleet controller and audit templating contexts for potential misuse.

Generated by OpenCVE AI on September 3, 2026 at 16:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
First Time appeared Suse
Suse fleet
Vendors & Products Suse
Suse fleet

Thu, 03 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Description A security vulnerability was discovered in Fleet's Helm template preprocessing where templates evaluated by the Fleet controller could reach network resources outside the management cluster. A user who can supply bundle content to a repository referenced by a `GitRepo` resource can cause the Fleet controller to: - Disclose cluster metadata available to the templating context. - Reveal information about hosts reachable from the controller's network position. Because the disclosure channel is name resolution, it may remain effective in environments where outbound traffic is otherwise restricted. The disclosed information is limited to values exposed to the Fleet templating context and to name resolution results. Integrity and availability of managed clusters are not affected. This issue affects Fleet: from 0.12.0 before 0.12.19, from 0.13.0 before 0.13.15, from 0.14.0 before 0.14.10, from 0.15.0 before 0.15.6, and from 0.16.0 before 0.16.1.
Title Fleet: DNS exfiltration via Sprig getHostByName in fleet.yaml Helm template preprocessing
Weaknesses CWE-1336
CWE-918
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: suse

Published:

Updated: 2026-09-03T15:15:25.490Z

Reserved: 2026-08-17T15:22:54.444Z

Link: CVE-2026-75036

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-03T16:18:22.607

Modified: 2026-09-03T16:25:43.557

Link: CVE-2026-75036

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T15:40:29Z

Weaknesses
  • CWE-1336

    Improper Neutralization of Special Elements Used in a Template Engine

  • CWE-918

    Server-Side Request Forgery (SSRF)