CVE-2026-113620
In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, operator …
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- gitlab.eclipse.org/security/cve-assignment/-/work_items/468
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1267
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1269
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1270
- nvd.nist.gov/vuln/detail/CVE-2026-113620
- cve.org/CVERecord?id=CVE-2026-113620
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.