cilium-agent container can access the host via `hostPath` mount
Published 17 Mar 2023 · Updated 10 Sept 2026
Is your project on an affected github.com/cilium/cilium?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.11.15
- Fixed in
- 1.11.15
go get github.com/cilium/cilium@v1.11.15- Affected
- >=1.12.0 <1.12.8
- Fixed in
- 1.12.8
go get github.com/cilium/cilium@v1.12.8- Affected
- >=1.13.0 <1.13.1
- Fixed in
- 1.13.1
go get github.com/cilium/cilium@v1.13.1Details
Impact
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.
Patches
The issue has been fixed and is available on versions >=1.11.15, >=1.12.8, >=1.13.1.
Workarounds
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.
References
Acknowledgements
The Cilium community has worked together with members of Isovalent and Form3 to prepare these mitigations. Special thanks to Anastasios Koutlis, Daniel Teixeira, and Magdalena Oczadly for their cooperation.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
Is GHSA-4hc4-pgfx-3mrx in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cilium/cilium, and gives you the command that fixes it.
More advisories for github.com/cilium/cilium
- LowCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces in github.com/cilium/cilium · 1 Oct 2026
- MediumCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces · 24 Sept 2026
- LowCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match in github.com/cilium/cilium · 10 Sept 2026
- MediumCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match · 3 Sept 2026
- LowCVE-2026-49445Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access in github.com/cilium/cilium · 7 Jul 2026
- LowCVE-2026-53935CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation in github.com/cilium/cilium · 7 Jul 2026
References
- Linkgithub.com/cilium/cilium/security/advisories/GHSA-4hc4-pgfx-3mrx
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-27593
- Linkgithub.com/cilium/cilium/pull/24075
- Packagegithub.com/cilium/cilium
- Linkgithub.com/cilium/cilium/releases/tag/v1.11.15
- Linkgithub.com/cilium/cilium/releases/tag/v1.12.8
- Linkgithub.com/cilium/cilium/releases/tag/v1.13.1
- Linkkubernetes.io/docs/reference/access-authn-authz/rbac
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.