# CVE-2026-44938: Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent

> An attacker with git push access can bypass Pod Security Standards by overwriting namespace labels, allowing deployment of restricted workloads.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-864g-863m-vcvq, GO-2026-5871

## What is CVE-2026-44938?

CVE-2026-44938 is a high-severity vulnerability in SUSE Rancher, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleDeployment.spec.options.namespaceLabels) when applying them to the target namespace.

An attacker with git push access to a
 Fleet-monitored repository could overwrite Pod Security Standards (PSS)
 enforcement labels on a target namespace. This allows the attacker to 
weaken admission controls and deploy workloads that PSS policies would 
otherwise block.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-44938?

9 open source packages ship an affected version, including github.com/rancher/fleet. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/fleet` | Go | From 0.12.0 | 0.12.15, 0.13.11, 0.14.6, 0.15.2 |
| `github.com/rancher/fleet` | Go | From 0.12.0 | 0.12.15 |
| `github.com/rancher/fleet` | Go | From 0.12.0 | 0.12.15 |
| `github.com/rancher/fleet` | Go | From 0.13.0 | 0.13.11 |
| `github.com/rancher/fleet` | Go | From 0.13.0 | 0.13.11 |
| `github.com/rancher/fleet` | Go | From 0.14.0 | 0.14.6 |
| `github.com/rancher/fleet` | Go | From 0.14.0 | 0.14.6 |
| `github.com/rancher/fleet` | Go | From 0.15.0 | 0.15.2 |
| `github.com/rancher/fleet` | Go | From 0.15.0 | 0.15.2 |

Products: Suse Rancher Fleet.

## How do I fix CVE-2026-44938?

Upgrade github.com/rancher/fleet to a fixed version for your release line: 0.12.15, 0.13.11, 0.14.6 or 0.15.2.

## Is CVE-2026-44938 being exploited?

There is no known exploitation of CVE-2026-44938 in the wild and no public exploit code.

## Other vulnerabilities in SUSE Rancher

- [CVE-2026-44935](https://insights.sbomify.com/CVE-2026-44935/): Rancher Fleet vulnerable to cross namespace secret disclosure via unvalidated `valuesFrom` references in Helm Deployer (critical 9.9)
- [CVE-2026-41050](https://insights.sbomify.com/CVE-2026-41050/): Helm impersonation bypass of `RESTClientGetter` retains `cluster-admin` during template rendering (critical 9.9)
- [CVE-2026-88808](https://insights.sbomify.com/CVE-2026-88808/): Privilege escalation in Rancher (high 8.8)
- [CVE-2026-44937](https://insights.sbomify.com/CVE-2026-44937/): SUSE Rancher Fleet had an Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components (high 8.3)
- [CVE-2026-93538](https://insights.sbomify.com/CVE-2026-93538/): Missing authorization in Rancher (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44938 and fix it if it is affected.

What it is: CVE-2026-44938 is a high-severity vulnerability in SUSE Rancher, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44938 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/fleet (Go): affected from 0.12.0; fixed in 0.12.15, 0.13.11, 0.14.6, 0.15.2
- github.com/rancher/fleet (Go): affected from 0.12.0; fixed in 0.12.15
- github.com/rancher/fleet (Go): affected from 0.12.0; fixed in 0.12.15
- github.com/rancher/fleet (Go): affected from 0.13.0; fixed in 0.13.11
- github.com/rancher/fleet (Go): affected from 0.13.0; fixed in 0.13.11
- github.com/rancher/fleet (Go): affected from 0.14.0; fixed in 0.14.6
- github.com/rancher/fleet (Go): affected from 0.14.0; fixed in 0.14.6
- github.com/rancher/fleet (Go): affected from 0.15.0; fixed in 0.15.2
- github.com/rancher/fleet (Go): affected from 0.15.0; fixed in 0.15.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44938/ (Markdown: https://insights.sbomify.com/CVE-2026-44938/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44938
- OSV: https://osv.dev/vulnerability/CVE-2026-44938

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44938/
Summaries are generated and may contain mistakes; the official description above is the record.