Description
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, an attacker with access to a Cilium agent pod can write to `/opt/cni/bin` due to a `hostPath` mount of that directory in the agent pod. By replacing the CNI binary with their own malicious binary and waiting for the creation of a new pod on the node, the attacker can gain access to the underlying node.The issue has been fixed and the fix is available on versions 1.11.15, 1.12.8, and 1.13.1. Some workarounds are available. Kubernetes RBAC should be used to deny users and service accounts `exec` access to Cilium agent pods. In cases where a user requires `exec` access to Cilium agent pods, but should not have access to the underlying node, no workaround is possible.
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| cilium | — | — |
| cilium-operator | — | — |
| cilium-proxy | — | — |
| github.com/cilium/cilium | — | — |
| hubble | — | — |
| hubble-relay | — | — |
| hubble-ui | — | — |
| hubble-ui-backend | — | — |
References
Similar Threats
- Unknown CLEANSTART-2026-BR79647
- Unknown CLEANSTART-2026-GB36430
- Unknown CLEANSTART-2026-QR52625
- High CVE-2024-28860
- High CVE-2024-28248
Free Vulnerability Check
Is your WordPress site affected?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.