Back to CVE records
Critical 9.8Published Oct 20, 2026

CVE-2026-113620Eclipse ioFog operator WebSocket accepts an unverified JWT

Updated under an hour ago ()

Does this affect you?

It affects Eclipse Foundation Eclipse ioFog. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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
9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-347
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
eclipse
NVD analysis
Awaiting Analysis
Record last updated
Oct 20, 2026
First seen by InfoSec Signals
Oct 20, 2026

Affected products

Affected products
Eclipse Foundation Eclipse ioFog
eclipse_foundation:eclipse_iofog (from the name)
from 3.8.0 through 3.9.1
CNA record

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.