CVE-2026-86671: CWE-918 in Eclipse Foundation Eclipse Che

In Eclipse Che versions 7.29.0 and later, the endpoints GET /api/scm/resolve and POST /api/factory/resolver pass an attacker-controlled URL to URLFetcher.fetch(), which invokes new URL(url).openConnection() without validating the URL scheme or host. This lack of validation permits any authenticated user to read arbitrary local files via the file:// scheme, including sensitive files such as the Kubernetes service-account token. Additionally, users can access internal HTTP services and cloud instance metadata endpoints (e.g., 169.254.169.254). The stored SCM personal access token is forwarded as an Authorization header to arbitrary hosts specified by the attacker. Furthermore, when a victim opens a workspace from a malicious devfile with a parent.uri pointing to an attacker-controlled server, the SCM PAT can be exfiltrated without direct API access. There is currently no available patch or fix for this vulnerability.

An attacker with authenticated access to Eclipse Che can read arbitrary local files on the pod, including sensitive Kubernetes service-account tokens, access internal HTTP services and cloud metadata endpoints, and exfiltrate stored SCM personal access tokens by forwarding them to attacker-controlled hosts. This can lead to unauthorized access to internal resources and compromise of cloud and source code management credentials. The vulnerability also enables credential theft through malicious devfiles without requiring direct API access.

No fix is currently available for this vulnerability. Users should exercise caution by limiting authenticated user access to trusted individuals only and avoid opening workspaces from untrusted or malicious devfiles. Monitor for suspicious activity related to SCM token usage and internal resource access. Check the vendor advisory regularly for updates on remediation.