Read the docs
TI-2026-76882 Aliases CVE-2026-113620GHSA-26cx-x379-5j5c

Eclipse ioFog operator WebSocket accepts an unverified JWT

Priority MEDIUM 49CWE-347Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-347.

Summary

Eclipse ioFog Controller versions 3.8.0 through 3.9.1 accept operator WebSocket upgrades on the exec and log routes without verifying the bearer JWT. The payload is decoded and its groups or roles are used as RBAC subjects (CWE-347). A self-minted token with an admin group matches the built-in admin role, so a remote attacker who knows the UUID of a microservice or fog can open an exec or log session. HTTP routes verify the token before RBAC and are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00286 21st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Eclipse FoundationEclipse ioFog3.8.0 – 3.9.1—No fix listedCNA
  • Eclipse ioFog VendorEclipse Foundation Affected 3.8.0 – 3.9.1 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Eclipse ioFog.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Timeline

  1. 2026-10-20 Threatist record created from CVE-2026-113620
  2. 2026-10-20 Alias added: GHSA-26cx-x379-5j5c

References

Other 4

  • TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
  • TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
  • TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
  • TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
  • TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
  • TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
See all 466 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences