A cross-tenant authorization issue was discovered in SUSE Rancher Fleet. During agent-initiated cluster registration, cluster labels supplied by the registering agent, including labels in the reserved management.cattle.io/ namespace such as the cluster display name label, were applied to the resulting upstream Cluster object. Because Fleet resolves GitRepo and Bundle targets from those cluster labels, a party able to register a cluster into a Fleet workspace namespace shared with other tenants could cause its own cluster to satisfy targeting rules that administrators intended for a different cluster. This affects SUSE Rancher Fleet 0.16 before 0.16.1, 0.15 before 0.15.6, 0.14 before 0.14.10, 0.13 before 0.13.15, 0.12 before 0.12.19 and older versions.
CVE-2026-93538
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 32EG Risk 32/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 5th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 28, 2026
Last Modified
September 29, 2026
Advisory Details (1)
Auto-updated Sep 28, 2026Cross-tenant BundleDeployment and Secret disclosure via spoofed cluster labels during agent-initiated registration in Fleet · Advisory · rancher/fleet · GitHub
https://github.com/rancher/fleet/security/advisories/GHSA-h9p5-fp5h-qpqrWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 01:06 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 00:33 UTCEG score recompute
- 2026-10-02 00:02 UTCEG score recompute
- 2026-10-01 19:51 UTCEPSS rescore
- 2026-09-30 22:48 UTCEG score recompute
- 2026-09-30 15:04 UTCEPSS rescore
- 2026-09-29 18:11 UTCEG score recompute
- 2026-09-29 05:51 UTCEG score recompute
- 2026-09-28 17:35 UTCEG score recompute
- 2026-09-28 16:34 UTCEG score recompute
- 2026-09-28 15:27 UTCEG score recompute
- 2026-09-28 14:27 UTCEG score recompute
- 2026-09-28 14:26 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-93538?
When was CVE-2026-93538 disclosed?
Is CVE-2026-93538 actively exploited?
What is the CVSS score of CVE-2026-93538?
How do I remediate CVE-2026-93538?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93538
Is Your Infrastructure Affected by CVE-2026-93538?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.