18 matches found
CVE-2026-115216
In Eclipse ioFog Operator versions 3.8.0 before 3.9.2, TLS certificate verification is disabled when the operator contacts the Controller API and when it logs in to an external OIDC issuer. An on-path attacker can present any certificate, capture the OAuth client secret external mode or the...
CVE-2026-113644
In Eclipse ioFog iofogctl versions 1.0.0 through 3.7.0 and 3.8.0-rc.1 through 3.9.1, the provisioning key and CA certificate returned by the Controller API are concatenated into shell commands edgelet provision and edgelet config cert on supported releases; iofog-agent provision and iofog-agent...
CVE-2026-113644 iofogctl command injection via Controller provisioning response
In Eclipse ioFog iofogctl versions 1.0.0 through 3.7.0 and 3.8.0-rc.1 through 3.9.1, the provisioning key and CA certificate returned by the Controller API are concatenated into shell commands edgelet provision and edgelet config cert on supported releases; iofog-agent provision and iofog-agent...
CVE-2026-113644
Eclipse ioFog iofogctl versions 1.0.0 through 3.7.0 and 3.8.0-rc.1 through 3.9.1 are vulnerable to command injection . The root cause is the unsanitized concatenation of the provisioning key and CA certificate from the Controller API into shell commands (such as edgelet provision or iofog-agent p...
EUVD-2026-110762
In Eclipse ioFog iofogctl versions 1.0.0 through 3.7.0 and 3.8.0-rc.1 through 3.9.1, the provisioning key and CA certificate returned by the Controller API are concatenated into shell commands edgelet provision and edgelet config cert on supported releases; iofog-agent provision and iofog-agent...
CVE-2026-115216 Eclipse ioFog Operator disables TLS certificate verification when sending Controller and OIDC credentials
In Eclipse ioFog Operator versions 3.8.0 before 3.9.2, TLS certificate verification is disabled when the operator contacts the Controller API and when it logs in to an external OIDC issuer. An on-path attacker can present any certificate, capture the OAuth client secret external mode or the...
CVE-2026-115216
Eclipse ioFog Operator versions 3.8.0 before 3.9.2 are vulnerable to a security flaw where TLS certificate verification is disabled during communication with the Controller API and external OIDC issuers. This allows an on-path attacker to present any certificate to intercept sensitive credentials...
EUVD-2026-110758
In Eclipse ioFog Operator versions 3.8.0 before 3.9.2, TLS certificate verification is disabled when the operator contacts the Controller API and when it logs in to an external OIDC issuer. An on-path attacker can present any certificate, capture the OAuth client secret external mode or the...
PT-2026-126388
In Eclipse ioFog Operator versions 3.8.0 before 3.9.2, TLS certificate verification is disabled when the operator contacts the Controller API and when it logs in to an external OIDC issuer. An on-path attacker can present any certificate, capture the OAuth client secret external mode or the...
PT-2026-126387
In Eclipse ioFog iofogctl versions 1.0.0 through 3.7.0 and 3.8.0-rc.1 through 3.9.1, the provisioning key and CA certificate returned by the Controller API are concatenated into shell commands edgelet provision and edgelet config cert on supported releases; iofog-agent provision and iofog-agent...
CVE-2026-113619
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...
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,...
EUVD-2026-104989
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,...
CVE-2026-113620 Eclipse ioFog operator WebSocket accepts an unverified JWT
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,...
CVE-2026-113620
In Eclipse ioFog Controller versions 3.8.0 through 3.9.1 , a vulnerability exists where operator WebSocket upgrades on the exec and log routes fail to verify the bearer JWT . The system decodes the payload and uses the contained groups or roles as RBAC subjects . An attacker can provide a self-mi...
CVE-2026-113619 Eclipse ioFog renders request templates before authentication
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...
EUVD-2026-104987
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...
CVE-2026-113619
Eclipse ioFog Controller versions 3.8.0 through 3.9.1 is vulnerable to an uncontrolled resource consumption issue (CWE-400). The Liquid engine renders POST, PUT, and PATCH request bodies containing template substitutions before performing authentication or RBAC checks. Because the bearer check fa...