Live › vulnerability › CVE-2026-113620
Go to dashboardioFog Controller 3.8.0 through 3.9.1 accepts unsigned JWTs on the operator WebSocket exec and log routes and uses the token's groups claim for RBAC. A forged token with groups:[admin] gives an interactive shell in any running microservice container, and live logs, for anyone who can reach the controller API port and knows a microservice or fog UUID. UUIDs can be listed with the same forged admin access. HTTP routes and agent sockets are not affected. Fixed in 3.9.2.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| eclipse-iofog-controller | other | >= 3.8.0, <= 3.9.1 | 3.9.2 |
3.8.0 to 3.9.1 is affected), for example iofogctl version or the image tag of the controller deployment3.9.2Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-113620")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.