# CVE-2026-44947: Stale PSA ClusterRoleBinding Persists After RoleTemplate Downgrade in Rancher

> Users retain unauthorized Pod Security Admission permissions after RoleTemplate downgrades due to missing cleanup in Rancher.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-c4rp-wgqc-mfhc

## What is CVE-2026-44947?

CVE-2026-44947 is a medium-severity missing authorization vulnerability in SUSE Rancher, published on 30 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A missing clean-up in the legacy Project Role Template Binding (PRTB) 
reconciler in Rancher versions 2.13.0 up to 2.13.7 and 2.14.0 up to 2.14.3 allowed users to retain unauthorized Pod Security 
Admission (PSA) permissions after an administrator removes those 
permissions from a RoleTemplate.

Weakness: CWE-281 (Improper Preservation of Permissions)

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


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

No fix has been published for CVE-2026-44947 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44947 is a medium-severity missing authorization vulnerability in SUSE Rancher, published on 30 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44947 in the wild and no public exploit code.

Affected product: SUSE Rancher. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-44947/ (Markdown: https://insights.sbomify.com/CVE-2026-44947/index.md)
```

## Sources

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

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