dbcve.org
CWE-281Weakness · CWE-281

CVE-2026-44947

MEDIUM · 6.9 CVSS v4.0 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The legacy Project Role Template Binding (PRTB) reconciler in Rancher fails to clean up existing bindings when an administrator removes PSA permissions from a RoleTemplate. This causes stale bindings to persist, allowing users to retain unauthorized Pod Security Admission permissions even after those permissions have been revoked by an administrator.

MitigationAdministrators should audit existing PRTBs for unauthorized permissions and manually remove stale bindings, then upgrade to versions 2.13.8+ and 2.14.4+ when available to prevent future accumulation of zombie permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rancher version
    Check the Rancher pod image tag or Helm chart version in the management cluster. Compare against known affected version ranges (2.13 versions before 2.13.8, 2.14 versions before 2.14.4).
    Affected if Rancher version falls within the affected range and PSA-based RoleTemplates are in use.
  2. List RoleTemplates with PSA configurations
    Use kubectl or the Rancher API to retrieve all RoleTemplates. Inspect each RoleTemplate's rules for PodSecurityAdmission (PSA) permissions by checking for rule subjects with apiGroup matching the PSA admission API.
    Affected if Any RoleTemplate currently or previously configured with PSA rules exists in the system.
  3. Enumerate all Project Role Template Bindings
    Query all PRTB resources across all namespaces: kubectl get prtb --all-namespaces or equivalent API call. Extract the RoleTemplate name referenced by each binding.
    Affected if PRTB resources exist that reference RoleTemplates.
  4. Detect stale PRTB bindings
    Cross-reference each PRTB's referenced RoleTemplate against the current RoleTemplate configuration. Identify bindings where the referenced RoleTemplate no longer contains PSA rules, or where PSA permissions were removed after the binding was created.
    Affected if PRTBs exist that grant PSA permissions that are no longer defined in their referenced RoleTemplate, indicating stale bindings.
  5. Audit user permissions from PRTBs
    Review the accumulated permissions for users/serviceaccounts bound via PRTBs. Check if any user retains PSA permissions (via clusterrole/role bindings derived from PRTBs) that are no longer authorized in the current RoleTemplate configuration.
    Affected if Users or service accounts retain PSA admission permissions through PRTBs that should have been revoked.

A user is affected if PRTBs exist that grant PSA permissions which were subsequently removed from the corresponding RoleTemplate, leaving stale bindings that grant unauthorized access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Administrators should audit existing PRTBs for unauthorized permissions and manually remove stale bindings, then upgrade to versions 2.13.8+ and 2.14.4+ when available to prevent future accumulation of zombie permissions.

Recommended fix Moderate confidence

Rancher 2.13.8 or 2.14.4 (or later stable releases)

  1. Upgrade Rancher to version 2.13.8 or later to address the missing clean-up in the legacy PRTB reconciler
  2. Alternatively, upgrade to version 2.14.4 or later if using the 2.14 line
  3. After upgrade, verify that users no longer retain unauthorized PSA permissions after RoleTemplate permission removal
  4. Review existing Project Role Template Bindings to confirm permissions are correctly enforced post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data