Advisory record · GHSA-6x34-89p7-95wg

Rancher has downstream cluster privilege escalation through cluster and project role template binding (CRTB/PRTB)

CVSS 9.1 CriticalCriticalEPSS 0.010 · 63rd percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 3 Mar 2026, 14:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/rancher/rancherGo>=2.5.0, <2.5.16 || >=2.6.0, <2.6.72.5.16, 2.6.7
Identifiers
GHSA-6x34-89p7-95wg · CVE-2022-31247
Weakness (CWE)
CWE-285 · CWE-863
Published
3 Mar 2026
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Rancher versions 2.5.0 through 2.5.15 and 2.6.0 through 2.6.6 are vulnerable to privilege escalation through cluster and project role template bindings on downstream clusters. An authenticated user who can create or edit these bindings, such as a cluster owner or project owner, with kubectl access to the local cluster can gain owner rights in other projects or on other downstream clusters. Upgrade to Rancher 2.5.16, 2.6.7, or later; the source lists no other workaround beyond limiting access to trusted users.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H CNA (suse)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.