CVE-2026-113620 Eclipse Foundation CVE debrief

Who should care

Defenders responsible for Eclipse ioFog Controller deployments should assess exposure and prioritize patching or mitigation. This includes verifying the affected versions of Eclipse ioFog Controller and applying patches or mitigations to prevent exploitation. Additionally, defenders should review compensating controls for exposed systems while remediation is scheduled and verified, and check relevant monitoring, detection, and logs for exposed assets that

Why it matters

CVE-2026-113620 is a critical vulnerability in Eclipse ioFog Controller that allows an attacker to access exec or log sessions without proper authentication, requiring defenders to prioritize patching or mitigation.

• An attacker can access exec or log sessions for microservices or fogs without proper authentication.
• Defenders need to verify the affected versions of Eclipse ioFog Controller and apply patches or mitigations.
• The vulnerability can be exploited without authentication, making it a high-priority issue.

Technical summary

The vulnerability is caused by a lack of verification of the bearer JWT in operator WebSocket upgrades on the exec and log routes in Eclipse ioFog Controller versions 3.8.0 through 3.9.1. This allows an attacker to open an exec or log session for a microservice or fog whose UUID they already know. 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.

Defensive priority

Defenders should prioritize verifying the affected versions of Eclipse ioFog Controller and applying patches or mitigations to prevent exploitation.

Recommended defensive actions

• Verify the affected versions of Eclipse ioFog Controller in use
• Apply patches or mitigations to prevent exploitation
• Monitor for suspicious activity on exec and log routes
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The Eclipse ioFog Controller versions 3.8.0 through 3.9.1 are vulnerable to this issue. 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:

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.