CVE-2026-26963: Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled

Published Feb 19, 2026
·
Updated

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.

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 ciliumwg0 interface is explicitly routed to ciliumhost for policy enforcement. This ensures that host-level security policies are applied to decrypted WireGuard traffic. Execute the following configuration on each CiliumNode:

bash IPv4 Traffic ip rule add iif ciliumwg0 table 300 ip route add default dev ciliumhost table 300

IPv6 Traffic ip -6 rule add iif ciliumwg0 table 300 ip -6 route add default dev ciliumnet table 300

Acknowledgements

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 security@cilium.io. 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.

Other sources

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Versions 1.18.0 through 1.18.5 will incorrectly permit traffic from Pods on other nodes when Native Routing, WireGuard and Node Encryption are enabled. This issue has been fixed in version 1.18.6.

— NVD

Affected Software

2 affected componentsFixes available
go/github.com/cilium/cilium>=1.18.0<1.18.5
1.18.6
Cilium Cilium>=1.18.0<1.18.6

Event History

Feb 19, 2026
Advisory Published
via GitHub·07:39 PM
Data Sourced
via GitHub·07:39 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·11:38 PM
Data Sourced
via MITRE·11:38 PM
DescriptionSeverityWeakness
Feb 20, 2026
Data Sourced
via NVD·12:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 4, 58123
Event
via FIRST·03:12 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-26963?

CVE-2026-26963 is considered a medium severity vulnerability as it allows incorrect traffic permissions between Pods on different nodes.

2

How do I fix CVE-2026-26963?

To fix CVE-2026-26963, upgrade to Cilium version 1.18.6 or later.

3

What impact does CVE-2026-26963 have on my Kubernetes environment?

CVE-2026-26963 can lead to unauthorized traffic between Pods across different nodes, potentially compromising network security.

4

Which versions of Cilium are affected by CVE-2026-26963?

CVE-2026-26963 affects Cilium versions from 1.18.0 to 1.18.5, inclusive.

5

Is CVE-2026-26963 related to host policies in Cilium?

Yes, CVE-2026-26963 specifically involves host policies that incorrectly permit inter-node traffic.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203