Cpe:2.3:a:kubesphere:kubesphere:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3akubespherekubesphere/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 15 Sep 2026 13:40:43 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgSSRF Vulnerability in KubeSphere Git Credential Verificationhttps://feed.craftedsignal.io/briefs/2026-09-kubesphere-ssrf/Tue, 15 Sep 2026 13:40:43 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-kubesphere-ssrf/KubeSphere versions up to 4.1.3 contain a server-side request forgery (SSRF) vulnerability in the git credential verification endpoint, allowing authenticated attackers to exfiltrate Kubernetes Secrets.KubeSphere versions through 4.1.3 contain a server-side request forgery (SSRF) vulnerability located within the platform's git credential verification endpoint. The vulnerability arises because the endpoint fails to enforce allowlist restrictions on user-supplied URLs. An authenticated attacker can exploit this flaw to force the KubeSphere server to make unauthorized requests to internal network services. By manipulating the input and observing the subsequent error response handling, an attacker can exfiltrate basic-authentication credentials associated with Kubernetes Secrets located in any namespace within the cluster. This vulnerability, tracked as CVE-2026-91923, poses a significant risk to cluster integrity and sensitive data, as it allows for the escalation of privileges through the unauthorized access and retrieval of internal configuration and credential data.

Impact

Successful exploitation of this SSRF vulnerability allows an authenticated attacker to bypass intended network boundaries and access sensitive information, including basic-auth credentials stored within Kubernetes Secrets. This facilitates lateral movement and potentially full cluster compromise, as these secrets may contain keys for other services, databases, or third-party integrations.

Recommendation

  • Upgrade KubeSphere to a version beyond 4.1.3 to remediate CVE-2026-91923.
  • Audit access logs for the KubeSphere git credential verification endpoint to identify anomalous requests containing internal IP ranges or sensitive ports.
  • Apply network policies to restrict egress traffic from the KubeSphere controller/API pod to only required external endpoints, preventing internal network scanning.
]]>highadvisory