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.
0.2%(unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-115216 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115216?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115216?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115216 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
eclipse foundation:eclipse iofog
Versions
From the CNA's record in the CVE List.
Product
Affected
Eclipse Foundation Eclipse ioFog
from 3.8.0 before 3.9.2
Attack patterns (CAPEC)
CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.