CVE-2022-43755 is a high-severity use of insufficiently random values vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.6.0, < 2.6.10. It is fixed in 2.6.10, 2.7.1.
Impact An issue was discovered in Rancher versions up to and including 2.6.9 and 2.7.0, where the cattle-token secret, used by the cattle-cluster-agent, is predictable. Even after the token is regenerated, it will have the same value. This issue is not present in Rancher 2.5 releases. The cattle-token is used by Rancher's cattle-cluster-agent to connect to the Kubernetes API of Rancher provisioned downstream clusters. The problem occurs because the cattle-token secret does not use any random value in its composition, which causes it to always be regenerated with the same value. This can pose a serious problem if the token is compromised and needs to be recreated for security purposes. The usage of the cattle-token by an unauthorized user allows to escalate privileges to the cluster owner of the affected downstream cluster. It does not allow access to Rancher's own local cluster (the cluster where Rancher is provisioned). Workarounds In case it is not possible to promptly update to a patched version, a workaround is to use the rotate script provided in the public security advisory CVE-2021-36782 / GHSA-g7j7-h4q8-8w2f, which facilitates the rotation and creation of a new unique downstream cluster token. Patches Patched versions include releases 2.6.10, 2.7.1 and later versions. After upgrading to one of the patched versions, it is highly recommended to rotate the cattle-token in downstream clusters to guarantee that a new random token will be safely regenerated. The procedure below can rotate the cattle-token and should be executed in each downstream cluster provisioned by Rancher. It is recommended to first test this process in an appropriate development/testing environment. For more information If you have any questions or comments about this advisory: Reach out to SUSE Rancher Security team for security related inquiries. Open an issue in Rancher repository. Verify our support matrix and product support lifecycle.
Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.
CVE-2022-43755 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.6.10, 2.7.1). Upgrading removes the vulnerable code path.
go
github.com/rancher/rancher (>= 2.6.0, < 2.6.10)github.com/rancher/rancher (>= 2.7.0, < 2.7.1)github.com/rancher/rancher → 2.6.10 (go)github.com/rancher/rancher → 2.7.1 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2022-43755 is reachable in your applications. Explore open-source security for your team.
See if CVE-2022-43755 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2022-43755 in your environment →Upgrade the following packages to resolve this vulnerability:
github.com/rancher/rancher to 2.6.10 or latergithub.com/rancher/rancher to 2.7.1 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2022-43755 is a high-severity use of insufficiently random values vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.6.0, < 2.6.10. It is fixed in 2.6.10, 2.7.1. Security-sensitive operations rely on values that are predictable or insufficiently random.
CVE-2022-43755 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/rancher/rancher (go) versions >= 2.6.0, < 2.6.10 is affected.
Yes. CVE-2022-43755 is fixed in 2.6.10, 2.7.1. Upgrade to this version or later.
Whether CVE-2022-43755 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
github.com/rancher/rancher to 2.6.10 or latergithub.com/rancher/rancher to 2.7.1 or later