CVE-2026-26963: Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled
Impact Host Policies will incorrectly permit traffic from Pods on other nodes when all of the following configurations are enabled: Native Routing WireGuard Node Encryption (beta) These options are disabled by default in Cilium. Patches This issue was fixed by #42892.
Published Feb 19, 2026 · Updated Feb 20, 2026
Affected packages
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.18.0, < 1.18.5
- Fixed in
- 1.18.6
- Check
go list -m github.com/cilium/cilium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Host Policies will incorrectly permit traffic from Pods on other nodes when all of the following configurations are enabled:
These options are disabled by default in Cilium.
Patches
This issue was fixed by #42892.
This issue affects:
- Cilium v1.18 between v1.18.0 and v1.18.5 inclusive
This issue is fixed in:
- Cilium v1.18.6
Workarounds
There is currently no officially verified or comprehensive workaround for this issue. The following procedure has been validated strictly within a local 'Kind' environment and has not undergone exhaustive testing across diverse production architectures. Proceed with caution.
To mitigate the identified traffic bypass, ensure all ingress traffic from the cilium_wg0 interface is explicitly routed to cilium_host for policy enforcement. This ensures that host-level security policies are applied to decrypted WireGuard traffic. Execute the following configuration on each CiliumNode:
# IPv4 Traffic
ip rule add iif cilium_wg0 table 300
ip route add default dev cilium_host table 300
# IPv6 Traffic
ip -6 rule add iif cilium_wg0 table 300
ip -6 route add default dev cilium_net table 300Acknowledgements
Special thanks to @julianwiedmann for reporting the issue and helping with the resolution.
For more information
If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [email protected]. This is a private mailing list for the Cilium security team, and your report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.
Credited to julianwiedmann, smagnani96.
References
- https://github.com/cilium/cilium/security/advisories/GHSA-5r23-prx4-mqg3
- https://github.com/cilium/cilium/pull/42892
- https://github.com/cilium/cilium/commit/88e28e1e62c0b1a02c3f0fc22d888ac9eefbe885
- https://github.com/cilium/cilium/releases/tag/v1.18.6
- https://nvd.nist.gov/vuln/detail/CVE-2026-26963
- https://github.com/advisories/GHSA-5r23-prx4-mqg3
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-56742
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
medium5.9Sep 24, 2026CVE-2026-56743
Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
medium5.4Sep 3, 2026CVE-2026-49445
Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access
critical9.2Jul 6, 2026CVE-2026-53935
CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
medium6.9Jul 6, 2026CVE-2026-41520
Cillium exposes sensitive information included in the cilium-bugtool debug archive
high7.9Apr 25, 2026CVE-2026-33726
Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic
medium5.4Mar 26, 2026
