Quick answers
- Is CVE-2026-86671 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86671 being exploited in the wild.
- How severe is CVE-2026-86671?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Eclipse Che 7.29.0 and later.
- Is there a fix for CVE-2026-86671?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86671 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86671?
- Check whether you run Eclipse Che at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The `/api/scm/resolve` and `/api/factory/resolver` endpoints pass attacker-controlled URLs directly to URLFetcher without scheme or host validation, calling `new URL(url).openConnection()` and returning the response body. An authenticated attacker can exploit this Server-Side Request Forgery (SSRF) to access file://, internal HTTP services, and cloud metadata endpoints (169.254.169.254); SCM personal access tokens are automatically attached as Authorization headers to any destination. The vulnerability also affects users opening workspaces with malicious devfile parent.uri values, enabling credential theft without authentication.
Affected products
- Eclipse Che 7.29.0 and later
Timeline
- 2026-10-05: disclosed