CVE-2026-104615
Received Received - Intake

Cluster Identity Spoofing in SUSE Rancher Fleet

Publication date: 2026-10-30

Last updated on: 2026-10-30

Assigner: SUSE

Description
A security vulnerability was discovered in SUSE Rancher Fleet's cluster registration flow, in Fleet versions before 0.12, 0.13.0 up to 0.13.17, 0.14.0 up to 0.14.12, 0.15.0 up t o 0.15.17 and 0.16.0 up to 0.16.3. The cluster identity claimed by a registration request was accepted without being bound to the registration token that the request was made with. As a result, a registration request could be associated with a managed cluster that was originally registered with a different registration token.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-30
Last Modified
2026-10-30
Generated
2026-10-30
AI Q&A
2026-10-30
EPSS Evaluated
N/A
NVD
CVE-2026-104615
EUVD
EUVD-2026-114135

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
SUSE Rancher 0.16.0
SUSE Rancher 0.15.0.
SUSE Rancher 0.14.0
SUSE Rancher 0.13
SUSE Rancher 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-290 This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in SUSE Rancher Fleet allows an attacker to take over a cluster's identity by exploiting how registration tokens are handled. Fleet accepts a cluster identity without verifying it is bound to the correct registration token used in the request. This enables an attacker with a valid registration token and knowledge of another cluster's client identifier to obtain credentials scoped to that other cluster's Fleet management namespace.

Impact Analysis

An attacker could access Secrets and ConfigMaps synced into the affected namespace, modify bundle deployment and cluster status information, and disrupt Fleet management of the affected cluster by replacing the legitimate agent's credentials. This could lead to unauthorized access, data breaches, or service disruptions.

Mitigation Strategies

Upgrade Fleet to a patched version: v0.16.3, v0.15.17, v0.14.12, or v0.13.17. If immediate upgrade is not possible, use separate Fleet workspaces per tenant, restrict access to registration tokens, and monitor for unexpected registration activities.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-104615. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart