CVE-2026-115216Published Oct 27, 2026 · Oct 27Updated Nov 5
Eclipse ioFog Operator credential exposure in TLS connections
Eclipse Foundation Eclipse ioFog
Critical9.1
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse Foundation Eclipse ioFog |
| No fix yet |
Original description
In Eclipse ioFog Operator versions 3.8.0 before 3.9.2, TLS certificate verification is disabled when the operator contacts the Controller API and when it logs in to an external OIDC issuer. An on-path attacker can present any certificate, capture the OAuth client secret (external mode) or the Controller bootstrap admin password (embedded mode with Controller HTTPS enabled), and supply the access token the operator stores for later Controller API calls. v3.8 removed Keycloak. The exposed credential is not a Keycloak realm-admin secret.
From the CVE record · eclipse
References
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1064Exploit
- gitlab.eclipse.org/security/cve-assignment/-/work_items/519
- github.com/eclipse-iofog/iofog-operator/releases/tag/v3.9.2
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/115xxx/CVE-2026-115216.json
- nvd.nist.gov/vuln/detail/CVE-2026-115216