CVE-2019-11202 is a critical-severity improper authentication vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.0.0, <= 2.0.13. It is fixed in 2.2.2.
An issue was discovered that affects the following versions of Rancher: v2.0.0 through v2.0.13, v2.1.0 through v2.1.8, and v2.2.0 through 2.2.1. When Rancher starts for the first time, it creates a default admin user with a well-known password. After initial setup, the Rancher administrator may choose to delete this default admin user. If Rancher is restarted, the default admin user will be recreated with the well-known default password. An attacker could exploit this by logging in with the default admin credentials. This can be mitigated by deactivating the default admin user rather than completing deleting them.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2019-11202 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no 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.2.2). Upgrading removes the vulnerable code path.
go
github.com/rancher/rancher (>= 2.0.0, <= 2.0.13)github.com/rancher/rancher (>= 2.1.0, <= 2.1.8)github.com/rancher/rancher (>= 2.2.0, < 2.2.2)github.com/rancher/rancher → 2.2.2 (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-2019-11202 is reachable in your applications. Explore open-source security for your team.
See if CVE-2019-11202 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2019-11202 in your environment →Upgrade github.com/rancher/rancher to 2.2.2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2019-11202 is a critical-severity improper authentication vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.0.0, <= 2.0.13. It is fixed in 2.2.2. The application does not adequately verify the identity of a user, device, or process before granting access.
CVE-2019-11202 has a CVSS score of 9.8 (Critical). 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.0.0, <= 2.0.13 is affected.
Yes. CVE-2019-11202 is fixed in 2.2.2. Upgrade to this version or later.
Whether CVE-2019-11202 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.
Upgrade github.com/rancher/rancher to 2.2.2 or later.