CVE-2026-93537
Last modified
CVE-2026-93537 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. A user who can supply bundle content to a repository referenced by a GitRepo resource, for example through Git push access, or through permission to create or modify a GitRepo, can cause SUSE Rancher Fleet to read files from the filesystem of the environment that processes the bundle and include their contents in the generated Bundle resource. This can expose configuration or credential material that the user has no Kubernetes RBAC permission to read, including Helm registry credentials made available to the bundle-processing job when per-path Helm credentials are configured. This affects Fleet 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, 0.13 before 0.13.16, 0.12 before 0.12.20 and potentially older unsupported versions.. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
Description
A user who can supply bundle content to a repository referenced by a GitRepo resource, for example through Git push access, or through permission to create or modify a GitRepo, can cause SUSE Rancher Fleet to read files from the filesystem of the environment that processes the bundle and include their contents in the generated Bundle resource. This can expose configuration or credential material that the user has no Kubernetes RBAC permission to read, including Helm registry credentials made available to the bundle-processing job when per-path Helm credentials are configured. This affects Fleet 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, 0.13 before 0.13.16, 0.12 before 0.12.20 and potentially older unsupported versions.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Suse | Rancher Fleet | >= 0.12.0, < 0.12.20 |
| Suse | Rancher Fleet | >= 0.13.0, < 0.13.16 |
| Suse | Rancher Fleet | >= 0.14.0, < 0.14.11 |
| Suse | Rancher Fleet | >= 0.15.0, < 0.15.7 |
| Suse | Rancher Fleet | >= 0.16.0, < 0.16.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-93537?
How severe is CVE-2026-93537?
How do I fix CVE-2026-93537?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93531A weakness has been identified in gedelumbung HospitalManage…4.3
- CVE-2026-93532A security vulnerability has been detected in gedelumbung Ho…6.3
- CVE-2026-93533A vulnerability was determined in spatie Scotty up to 1.4.4.…6.3
- CVE-2026-93534A vulnerability was identified in spatie Scotty up to 1.4.2.…6.3
- CVE-2026-93535The Dark Mode – Improve Accessibility with AI Powered Dark T…6.4
- CVE-2026-93536A use after free caused by missing lifecycle management of g…5.3
- CVE-2026-93538A cross-tenant authorization issue was discovered in SUSE Ra…7.1
- CVE-2026-93539A vulnerability was discovered in Fleet's Git webhook receiv…5.4
- CVE-2026-9354A vulnerability was detected in NousResearch hermes-agent up…6.5
- CVE-2026-93540A privilege mismatch was found in Fleet. When a bundle reque…6.5
- CVE-2026-93541An out-of-bounds read in libXi's XQueryDeviceState() in libX…6.5
- CVE-2026-93542An out-of-bounds read in libXi's XI2 class parsing via size_…6.5
Are you affected by CVE-2026-93537?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST