Eclipse ioFog up to 3.9.1 Liquid engine resource consumption

Summaryinfo

A vulnerability was found in Eclipse ioFog up to 3.9.1. It has been rated as problematic. Impacted is an unknown function of the component Liquid engine. This manipulation causes resource consumption. The identification of this vulnerability is CVE-2026-113619. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in Eclipse ioFog up to 3.9.1 and classified as problematic. Affected by this vulnerability is an unknown function of the component Liquid engine. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

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.

It is possible to read the advisory at gitlab.eclipse.org. This vulnerability is known as CVE-2026-113619 since 10/20/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Eclipse

Name

• ioFog

Version

• 3.9.0
• 3.9.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion