Live › vulnerability › CVE-2026-113619
Go to dashboardEclipse ioFog Controller versions 3.8.0 through 3.9.1 render POST, PUT and PATCH bodies through an uncapped Liquid template engine before checking authentication. A small unauthenticated JSON body can stall or abort the Controller process, taking down the control plane, agent API and WebSocket relays.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Eclipse ioFog Controller 3.8.0 through 3.9.1 that expose its API to a network where unauthenticated callers can reach routes with template substitution enabled. The sources do not say whether the default configuration enables template substitution, so treat any reachable Controller in that range as in scope. Deployments where the Controller API is reachable only from trusted networks have lower exposure.
No product ranges from the sources yet.
3.8.0 through 3.9.13.9.1 (unknown: the sources do not name the fixed release)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, POST, PUT, and PATCH bodies on routes that enable template substitution are rendered by an uncapped Liquid engine before authentication and RBAC. The bearer check does not reject a missing or invalid token, and the auth rate limit applies only to user login routes. A small JSON body can stall or abort the Controller process. The anonymous caller does not receive the rendered result; the impact is availability of the control plane, including the agent API and in-process WebSocket relays on that process.
This page as .md · .json · in your agent: get_signal("CVE-2026-113619")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.