Eclipse Che versions 7.29.0 and later allow authenticated users to trigger the application to fetch arbitrary URLs via the /api/scm/resolve and /api/factory/resolver endpoints. The URLFetcher component accepts URL strings with no scheme or host allow‑list, constructs a java.net.URL object, and returns the request body to the caller. This flaw gives an attacker the ability to read local files on the Che environment through the file:// scheme, to contact internal services such as the Kubernetes pod service‑account token at /var/run/secrets/kubernetes.io/serviceaccount/token and the instance metadata service at 169.254.169.254, and to forward stored source code management personal access tokens as an Authorization header to a host of the attacker’s choosing. Additionally, malware embedded in a devfile’s parent.uri can exploit the same credential‑forwarding behavior when a user opens a workspace, enabling exfiltration of the user's SCM PAT without direct API interaction.

The affected product is Eclipse Che supplied by the Eclipse Foundation. Versions 7.29.0 and later are impacted. Specific patch information is not provided and no official fix has been released. The vulnerability is active across all deployments of these versions, regardless of the underlying Kubernetes cluster configuration.

The CVSS score is 8.4, indicating a high severity and implying significant impact if exploited. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, making it unclear how frequently it is exploited in the wild. Because the flaw allows local file reads, credential leakage, and conditional access to internal endpoints, an attacker with authenticated access could exfiltrate sensitive data and compromise the Kubernetes cluster. The absence of a vendor patch forces operators to rely on mitigations that restrict network access, enforce URL whitelisting, and remove or isolate devfile parent URIs to prevent credential forwarding.