Zero Radar
← feed
CriticalVulnerabilityCVE-2026-113620updated 25 Oct 2026, 15:20 UTC

Eclipse ioFog Controller lets anyone with a forged token open admin sessions

Attackers can forge a login token that the controller trusts for certain live connections, giving them admin-level access to run commands or read logs on your fog nodes and microservices. No password or account is needed.

Official, 2 sources
SeverityCriticalCVSS 9.8 of 10
Being exploited?UnclearNo reports either way yet
Fix available?UnclearNo fixed version published in the sources yet
How sure is this?Official, 2 sourcesBacked by an official source

How the attack works simplified

  1. 1Attacker forges tokenSelf-minted JWT with admin group
  2. 2Opens WebSocketExec or log route, known UUID
  3. 3Controller skips verificationJWT signature is never checked
  4. 4RBAC matches adminGroups treated as trusted roles
  5. ResultAttacker gets exec or log access

What happened

In Eclipse ioFog Controller 3.8.0 through 3.9.1, WebSocket upgrade requests on the exec and log routes decode the bearer JWT without verifying its signature, then use its groups or roles directly for RBAC decisions. A self-minted token with an admin group matches the built-in admin role.

Why it is dangerous: An attacker who knows the UUID of a microservice or fog can open an exec or log session on it and gain control of that workload, with no account and no RoleBinding required. Anyone running affected ioFog Controller versions exposed to a network the attacker can reach is at risk.

Are you affected?

You are affected if you run Eclipse ioFog Controller versions 3.8.0 through 3.9.1 and its exec or log WebSocket routes are reachable.

Eclipse ioFog Controller 3.8.0 through 3.9.1

What to do

  1. Check whether your ioFog Controller version is between 3.8.0 and 3.9.1
  2. Restrict network access to the controller, especially the exec and log WebSocket routes
  3. Check the Eclipse ioFog project advisory for a fixed version and upgrade as soon as one is published

Timeline

  1. 20 Oct 2026, 13:16 UTC
    Publicly disclosed
  2. 20 Oct 2026, 13:16 UTC
    Reported by NVD · NVD
  3. 25 Oct 2026, 15:20 UTC
    GitHub Advisory reported on it · GitHub Advisory

Sources 2 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-113620 · GHSA-26cx-x379-5j5c
CVSS
9.8 / 10
EPSS
0.3% chance of exploitation within 30 days
Disclosed
20 Oct 2026, 13:16 UTC
On Zero Radar
before the radar started
Last change
25 Oct 2026, 15:20 UTC

The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works

Eclipse ioFog Controller lets anyone with a forged token open admin sessions · Zero Radar