Eclipse ioFog operator WebSocket accepts an unverified JWT
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.
CVE-2026-113620
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-113620
Eclipse ioFog
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "Eclipse Foundation",
"product": "Eclipse ioFog",
"versions": [
{
"status": "affected",
"version": "3.8.0",
"versionType": "semver",
"lessThanOrEqual": "3.9.1"
}
],
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-113620
Source reference:
/cveMetadata/cveId
Publisher severity
critical
Source reference: /containers/cna/metrics
- Event
- #42284 · Revision 1
- Added to Heist Feed
- Publisher date