Threat Intelligence Database

In Eclipse Ankaios versions 0.6.0 to before 1.0.4, `LogRule::matches` in the agent control-interface authorizer stops at the first wildcard pattern in a single rule instead of evaluating later entries, which can cause deny `LogRule` entries to be skipped and allow unauthorized access to another workload's logs.

In Eclipse Ankaios versions 0.1.0 through 1.0.2, the agent creates workload files and Control Interface named pipes (FIFOs) under a predictable path derived from the agent name and a hash of the workload's runtime configuration. If a directory or FIFO already exists at that path when the agent (re)starts, the agent reuses it based only on an existence and/or file-type check, without validating its owner or permissions. A local, unprivileged user with write access to the same base directory (by default under `$TMPDIR/ankaios`, e.g. shared `/tmp`) can pre-create this path hierarchy, including the two Control Interface FIFOs, before the agent starts. The agent then treats the attacker-owned FIFOs as the legitimate Control Interface for the targeted workload. The attacker can complete the Control Interface handshake and issue requests using that workload's configured `controlInterfaceAccess` permissions, allowing impersonation of the workload and, depending on its configured permissions, unauthorized reading and/or modification of the cluster's desired state.

Eclipse Ankaios versions 0.1.0 through 1.0.1 contain a vulnerability where the agent does not limit the length declared by a workload in a length-delimited protobuf message received via the Control Interface FIFO. This allows a workload with Control Interface access to specify an excessively large message length, causing unbounded memory allocation and potentially aborting the agent process. This results in loss of orchestration services for workloads managed by the affected agent.

Eclipse Ankaios versions 0.5.1 through 1.0.1 contain an authorization flaw in the agent-side Control Interface authorizer. The flaw arises when multi-segment allow rules start with a wildcard, allowing authenticated workloads to submit requests with empty field masks that bypass intended access restrictions. This can lead to unauthorized reading or modification of cluster state beyond the authorized scope. The vulnerability is tracked as CVE-2026-84173 and has a high severity rating.