CVE-2026-113620: Flaw in Eclipse ioFog Scores 9.8 on CVSS
A newly published critical vulnerability in Eclipse ioFog carries a CVSS score of 9.8. Here is what is affected and how to respond.

Key points
- CVE-2026-113620 affects Eclipse ioFog.
- CVSS 9.8 (Critical).
- No exploitation confirmed yet.
A critical security flaw tracked as CVE-2026-113620 has been published in the National Vulnerability Database for Eclipse ioFog, with a CVSS base score of 9.8.
At a glance
- CVE
- CVE-2026-113620
- Product
- Eclipse ioFog
- CVSS
- 9.8 Critical
- Weakness
- CWE-347
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Eclipse Foundation | Eclipse ioFog | up to 3.9.1 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-113620
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-113620?
CVE-2026-113620 is a CWE-347 vulnerability in Eclipse ioFog.
How severe is CVE-2026-113620?
It has a CVSS score of 9.8 Critical.
Is CVE-2026-113620 being exploited?
There is no public confirmation of exploitation at the time of publication.


