Advisory record · GHSA-g7j7-h4q8-8w2f

Rancher API and cluster.management.cattle.io object vulnerable to plaintext storage and exposure of credentials

CVSS 9.9 CriticalCriticalEPSS 0.042 · 91st percentile

Critical, because:

  • CVSS score 9.9: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 23 Sept 2022, 18:11 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-g7j7-h4q8-8w2f · CVE-2021-36782
Weakness (CWE)
CWE-312
Published
23 Sept 2022
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 store sensitive fields such as passwords, API keys and Rancher's service account token in plaintext on Kubernetes objects like cluster.management.cattle.io. Anyone with read access to those objects, including authenticated users with cluster or project roles, can retrieve the credentials, and the exposed service account token can let a standard user escalate to cluster administrator. Upgrade to Rancher 2.5.16, 2.6.7 or later, then rotate the service account token, since the upgrade does not rotate it.

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.9 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H CNA (suse)
  • CISA KEV Not listed.
  • EPSS 0.042, the 91st percentile, on 20 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.