CVE-2026-84173
nicheAuthorization Bypass via Wildcard Rules in Eclipse Ankaios Control Interface
Eclipse Ankaios versions v0.5.1 through v1.0.1 contain a flaw in the agent-side Control Interface authorizer: multi-segment allow rules whose first path segment is a wildcard (e.g., *.workloads.some_workload) are incorrectly evaluated when a workload sends a CompleteStateRequest or UpdateStateRequest with an empty field mask. The empty-mask request is wrongly authorized as matching the scoped rule, so an authenticated workload can read the complete cluster state or replace state outside the subtree it was restricted to. An attacker gains unauthorized disclosure or modification of other workloads' configuration and cluster state, though exploitation requires the workload to already be running with a scoped allow rule (local vector, high privileges per the CVSS 4.0 score of 8.3). Only deployments that use wildcard-leading multi-segment allow rules are affected; a rule consisting solely of * is intentionally unrestricted and unaffected. No public proof of concept, CISA KEV listing, or in-the-wild exploitation is known, and EPSS estimates only a 0.1% probability of exploitation within 30 days.
What to do: Upgrade to an Ankaios release that includes the authorizer fix (anything after v1.0.1) as soon as one is available. Until then, replace multi-segment Control Interface allow rules that begin with a wildcard, such as *.workloads.some_workload, with explicit paths like desiredState.workloads.some_workload, and audit authenticated workloads with scoped rules for unexpected full-state reads or out-of-scope state changes.
| Eclipse Foundation Ankaios | v0.5.1 through v1.0.1 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
- Weakness
- CWE-863
- Vector
- CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
In the news0 stories
No ingested article mentions this CVE yet.