CVE-2026-84173
HighCVSS 8.3Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
In Eclipse Ankaios versions v0.5.1 through v1.0.1, the agent-side Control Interface authorizer incorrectly evaluates multi-segment allow rules whose first path segment is a wildcard. An authenticated workload with restricted access can submit a CompleteStateRequest or UpdateStateRequest with an empty field mask, which may be incorrectly authorized, allowing read of the complete cluster state or modification outside its authorized subtree.
Risk Assessment
Risk of unauthorized disclosure or modification of cluster configuration and other workloads, potentially leading to confidentiality and integrity breaches.
Recommendation
Until a fix is installed, avoid multi-segment Control Interface allow-rule filter masks that begin with a wildcard, such as *.workloads.some_workload. Replace them with explicit paths like desiredState.workloads.some_workload.
Other vulnerabilities in Eclipse Ankaios
See all- CVE-2026-86836High
In Eclipse Ankaios versions 0.1.0 through 1.0.2, the agent creates workload files and Control Interface FIFOs under a predictable path derived from the agent name and a hash of the workload configuration. If the path already exists at agent startup, it is reused without validating owner or permissions, allowing a local user to impersonate the workload and modify cluster state.
- CVE-2026-85201Medium
In Eclipse Ankaios versions 0.1.0 through 1.0.1, the agent does not limit the length declared by a workload in a length-delimited protobuf message received through the Control Interface FIFO. A workload with Control Interface access can specify an excessive message length, causing unbounded memory allocation that may abort the agent process, resulting in loss of orchestration services.
Original NVD description (English source)
In Eclipse Ankaios versions v0.5.1 through v1.0.1, the agent-side Control Interface authorizer incorrectly evaluates multi-segment allow rules whose first path segment is a wildcard. An authenticated workload with access restricted by such a rule can submit a CompleteStateRequest or UpdateStateRequest with an empty field mask. The request may then be incorrectly authorized as matching the scoped rule, allowing the workload to read the complete cluster state or replace state outside its authorized subtree. This may result in unauthorized disclosure or modification of other workloads and cluster configuration. Only a rule consisting solely of * is intended to authorize an empty mask. Mitigation: Until an update containing the fix is installed, avoid multi-segment Control Interface allow-rule filter masks that begin with a wildcard, such as *.workloads.some_workload. Replace them with explicit paths such as desiredState.workloads.some_workload, where applicable. A filter mask consisting solely of * has different, intentionally unrestricted semantics and should only be used when full-state access is intended.