# CVE-2026-86671: Server-side request forgery in Eclipse Che

> Authenticated users can exploit Server-Side Request Forgery to read local files, access internal services, and exfiltrate SCM tokens via malicious URLs.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-c4vh-c3rq-3rgr

## What is CVE-2026-86671?

CVE-2026-86671 is a high-severity server-side request forgery vulnerability in Eclipse Che, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-73 (External Control of File Name or Path), CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-86671?


## How do I fix CVE-2026-86671?

No fix has been published for CVE-2026-86671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86671 being exploited?

There is no known exploitation of CVE-2026-86671 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86671 and fix it if it is affected.

What it is: CVE-2026-86671 is a high-severity server-side request forgery vulnerability in Eclipse Che, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86671 in the wild and no public exploit code.

Affected product: Eclipse Che. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86671/ (Markdown: https://insights.sbomify.com/CVE-2026-86671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86671
- OSV: https://osv.dev/vulnerability/CVE-2026-86671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86671/
Summaries are generated and may contain mistakes; the official description above is the record.