# CVE-2026-115216: Eclipse ioFog Operator disables TLS certificate verification when sending Controller and OIDC credentials


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-mvpf-rh77-cjfw

## What is CVE-2026-115216?

CVE-2026-115216 is a critical vulnerability in Eclipse ioFog, published on 27 Oct 2026. 

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-115216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115216 is a critical vulnerability in Eclipse ioFog, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115216 in the wild and no public exploit code.

Affected product: Eclipse ioFog. 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-115216/ (Markdown: https://insights.sbomify.com/CVE-2026-115216/index.md)
```

## Sources

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

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