Eclipse Che: Server-side request forgery and SCM token disclosure
Summary
Eclipse Che versions 7.29.0 and later pass attacker-controlled URLs to a fetcher without scheme or host restrictions. Any authenticated Che user can read local files, including the Kubernetes service-account token, reach internal HTTP services and cloud metadata endpoints, and have a stored SCM personal access token sent to a host of their choosing. The token theft also works when a victim opens a workspace from a malicious devfile.
Affected
- Eclipse Che 7.29.0 to before 7.123.0 (per CVE record)
- Endpoints: GET /api/scm/resolve and POST /api/factory/resolver
Fixed in
Unknown. No fix is confirmed by the vendor; the advisory states no fix is available.
Workaround
- Restrict who has Che accounts and workspace access
- Limit outbound network access from Che server and workspace pods, especially to link-local metadata addresses and internal ranges
- Do not open untrusted factory links or devfiles
- Rotate SCM personal access tokens that may have been exposed
- Reduce the Kubernetes service-account permissions and PAT scope and lifetime
Exploitation
- No known exploitation in the wild, no public proof of concept found (search coverage was limited)
- CISA SSVC: exploitation none, automatable no
Our recommendation
- Check whether Eclipse Che is deployed and which version runs
- Restrict Che user accounts to trusted users
- Restrict egress traffic from Che pods, particularly to 169.254.169.254 and internal networks
- Rotate SCM tokens if untrusted factory links or devfiles were opened
- Check the Eclipse advisory and NVD record for a fix and re-check after NVD analysis
- Also check for CVE-2026-114278 in che-machine-exec
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Eclipse Foundation work item CVE assignment gitlab.eclipse.org
- Eclipse Foundation vulnerability report 620 gitlab.eclipse.org
- Red Hat Jira CRW-11956 redhat.atlassian.net
- Strix AI CVE-2026-86671 www.strix.ai
- che-server pull request 1048 github.com
- OpenCVE Eclipse Che app.opencve.io
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 1 Nov 2026, 12:50.
Original description (NVD)
In Eclipse Che versions 7.29.0 and later, the GET `/api/scm/resolve` and `POST /api/factory/resolver` endpoints pass an attacker-controlled URL to `URLFetcher.fetch()`, which calls `new URL(url).openConnection()` with no scheme or host allow-list and returns the response body to the caller. Any authenticated Che user can read arbitrary local files via the file:// scheme (including the pod's Kubernetes service-account token at `file:///var/run/secrets/kubernetes.io/serviceaccount/token`), reach internal HTTP services and cloud instance metadata endpoints (169.254.169.254), and have their stored SCM personal access token attached as an `Authorization` header to a host of their choosing. The same credential-forwarding behavior also fires when a victim opens a workspace from a malicious devfile whose `parent.uri` points to an attacker-controlled server, enabling exfiltration of the victim's SCM PAT without direct API access. No fix is available.
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.