{
  "id": "CVE-2026-86671",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-86671",
  "published_at": "2026-10-05T16:21:57.738Z",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Che",
  "cvss": {
    "score": 8.4,
    "source": "cna",
    "vector": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-918",
  "cvss_by_source": {
    "cna": 8.4
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Eclipse Foundation",
        "product": "Eclipse Che",
        "ranges": [
          "\u003e= 7.29.0, \u003c 7.123.0"
        ],
        "fixed_in": [
          "7.123.0"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Eclipse Che to 7.123.0 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
