CVE-2026-113620: falha crítica em Eclipse ioFog
Eclipse ioFog operator WebSocket accepts an unverified JWT
Publicada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
28Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 9.8epss 0.3%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Produtos afetados
Eclipse Foundation · Eclipse ioFogCVEs relacionadas — Eclipse ioFog
No mesmo produto, das mais perigosas para as menos.
CVE-2026-113619HIGHEclipse ioFog renders request templates before authenticationEPSS 0.4%CVE-2026-115216CRITICALEclipse ioFog Operator disables TLS certificate verification when sending Controller and OIDC credentialsEPSS 0.2%CVE-2026-113644MEDIUMiofogctl command injection via Controller provisioning responseEPSS 0.2%
Referências
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/468https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1267https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1269https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1270