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


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-26cx-x379-5j5c

## What is CVE-2026-113620?

CVE-2026-113620 is a critical vulnerability in Eclipse ioFog, published on 20 Oct 2026. 

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-113620?


## How do I fix CVE-2026-113620?

No fix has been published for CVE-2026-113620 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113620 being exploited?

There is no known exploitation of CVE-2026-113620 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113620 and fix it if it is affected.

What it is: CVE-2026-113620 is a critical vulnerability in Eclipse ioFog, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113620 in the wild and no public exploit code.

Affected product: Eclipse ioFog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113620/ (Markdown: https://insights.sbomify.com/CVE-2026-113620/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113620
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113620
- OSV: https://osv.dev/vulnerability/CVE-2026-113620

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113620/
Summaries are generated and may contain mistakes; the official description above is the record.