Skip to content

Vendor

rancher vulnerabilities

80 published CVES affecting rancher, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
80
Critical
17
High
47
Medium
15
Low
0
Unscored
1
CISA KEV
0
Atom feed of rancher alerts

Products

Latest rancher CVEs

Newest publication first · page 1 of 4

  1. HighCVSS 8.8 EPSS 0.11%

    Rancher issues long-lived registration tokens to authenticate nodes and agents joining a downstream cluster. These tokens were stored and exposed in plaintext with no expiration, so a malicious user could obtain one either through the Rancher API, etcd, stored automation, or dire...

  2. HighCVSS 8.8 EPSS 0.44%

    A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleDeployment.spec.options.namespaceLabels) when applying them to the target namespace. An attacker with git push access to a...

  3. HighCVSS 8.7 EPSS 0.41%

    Local Path Provisioner provides a way for the Kubernetes users to utilize the local storage in each node. Prior to 0.0.36, a malicious user with permission to edit the local-path-config ConfigMap in the local-path-storage namespace can manipulate the helperPod.yaml template used...

  4. HighCVSS 8.4 EPSS 0.37%

    A vulnerability has been identified in Rancher's Extensions where malicious code can be injected in Rancher through a path traversal in the compressedEndpoint field inside a UIPlugin deployment. A malicious UI extension could abuse that to: * Overwrite Rancher binaries or configu...

  5. MediumCVSS 4.8 EPSS 0.17%

    A vulnerability has been identified within Rancher Manager, where using self-signed CA certificates and passing the -skip-verify flag to the Rancher CLI login command without also passing the –cacert flag results in the CLI attempting to fetch CA certificates stored in Rancher’s...

  6. HighCVSS 8.2 EPSS 0.52%

    A vulnerability has been identified within Rancher Manager in which it did not enforce request body size limits on certain public (unauthenticated) and authenticated API endpoints. This allows a malicious user to exploit this by sending excessively large payloads, which are fully...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.