CVE-2026-113620: critical vulnerability in Eclipse ioFog
Eclipse ioFog operator WebSocket accepts an unverified JWT
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.8epss 0.3%
In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, operator WebSocket upgrades on the exec and log routes do not verify the bearer JWT. The payload is decoded and its groups or roles are used as RBAC subjects. A self-minted token whose groups contain admin matches the built-in admin role, with no account and no RoleBinding. The attacker can open an exec or log session for a microservice or fog whose UUID they already know. HTTP routes are not affected: they verify the token before RBAC. Agent WebSockets verify the fog token and are not affected.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Eclipse Foundation · Eclipse ioFogRelated CVEs — Eclipse ioFog
In the same product, most dangerous first.
CVE-2026-113619HIGHEclipse ioFog renders request templates before authenticationEPSS 0.4%CVE-2026-115216CRITICALEclipse ioFog Operator disables TLS certificate verification when sending Controller and OIDC credentialsEPSS 0.2%CVE-2026-113644MEDIUMiofogctl command injection via Controller provisioning responseEPSS 0.2%
References
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/468https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1267https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1269https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1270