CVE-2026-113620
CVE-2026-113620 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-347.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- EPSS exploit prediction: 0% (21st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-347
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-113620?
- 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.
- How severe is CVE-2026-113620?
- CVE-2026-113620 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-113620 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-113620?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2026-113620 published?
- CVE-2026-113620 was published on 2026-10-20.
References
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/468
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1267
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1269
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1270
Other CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities
- CVE-2026-120387 — Critical (CVSS 10.0): An improper JWT signature verification vulnerability in CIRCUTOR PowerStudio SCADA WAVE desktop version allows an…
- CVE-2026-120017 — Critical (CVSS 10.0): SAP NetWeaver AS ABAP and ABAP Platform does not perform sufficient verification of incoming authentication assertions…
- CVE-2026-76482 — Critical (CVSS 10.0): As part of Cisco's ongoing commitment to proactive security and product quality, the engineering team for Cisco License…
- CVE-2026-5430 — Critical (CVSS 10.0): The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or…
- CVE-2026-56451 — Critical (CVSS 10.0): A vulnerability has been identified in Opcenter X (All versions < V2604). Affected applications do not properly…
- CVE-2026-48558 — Critical (CVSS 10.0): SimpleHelp versions 5.5.15 and prior and 6.0 pre-release versions contain an authentication bypass vulnerability in the…
Browse all CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities →