Quick answers
- Is CVE-2026-113620 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113620 being exploited in the wild.
- How severe is CVE-2026-113620?
- Critical severity, with a CVSS score of 9.8, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ioFog Controller 3.8.0 through 3.9.1.
- Is there a fix for CVE-2026-113620?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-113620 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-113620?
- Check whether you run Eclipse ioFog Controller at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper cryptographic signature verification (CWE-347) in the WebSocket upgrade handlers for /exec and /log routes. The controller decodes the bearer JWT without validating its signature and uses the unverified token's group/role claims for RBAC decisions, allowing an attacker to craft a self-signed token with admin groups. An attacker needs knowledge of a target microservice or fog UUID to open a session; REST HTTP routes are unaffected as they properly verify tokens before RBAC evaluation.
Affected products
- Eclipse ioFog Controller 3.8.0 through 3.9.1
Timeline
- 2026-10-20: disclosed: Published by NVD