Authenticated SSRF via unvalidated Cluster CRD endpoint
Published Aug 5, 2026 · Updated Aug 5, 2026
SSRF in KubeSphere 4.0.0 through 4.1.3-rc.0 allows remote authenticated users to make internal requests through Cluster CRDs. Cluster reconciliation parses KubernetesAPIEndpoint only for URL syntax, then calls Discovery().ServerVersion() without blocking internal destinations. Creating or updating a Cluster CRD is required, and requests originate from controller-manager and apiserver pods with access to internal or metadata services.
Summary
What happened
SSRF in KubeSphere 4.0.0 through 4.1.3-rc.0 allows remote authenticated users to make internal requests through Cluster CRDs. Cluster reconciliation parses KubernetesAPIEndpoint only for URL syntax, then calls Discovery().ServerVersion() without blocking internal destinations. Creating or updating a Cluster CRD is required, and requests originate from controller-manager and apiserver pods with access to internal or metadata services.
The record
- CVE
- CVE-2026-71208
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- KubeSphere
- Product
- KubeSphere
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0.0 <=4.1.3-rc.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo