The vulnerability lies in the Fleet Agent's deployer, which fails to filter security‑sensitive keys from namespaceLabels in fleet.yaml or BundleDeployment.spec.options. An attacker with write permission to a Fleet‑monitored Git repository can insert or overwrite Pod Security Standards labels on a target namespace. This manipulation weakens the admission controls that normally block non‑conforming workloads, enabling the attacker to deploy pods that PSS policies would otherwise deny. The flaw aligns with CWE‑522, reflecting an inadequate protection of sensitive information.

The issue affects the SUSE Rancher Fleet Agent. Specific affected product versions are not disclosed by the vendor; therefore the vulnerability is assumed to apply to all current releases until a patched version is released. When in doubt, verify the exact version deployed.

The CVSS score of 8.8 classifies the vulnerability as high severity, while the EPSS score of less than 1% indicates a very low but non‑zero likelihood of exploitation. The vulnerability is not listed in CISA KEV. Exploitation requires only git‑push rights to a Fleet‑monitored repository, a capability that many development teams grant. Consequently, environments with broad repository write access face a high risk of PSS bypass and malicious workload deployment.