GHSA-5R23-PRX4-MQG3
Vulnerability from github – Published: 2026-02-19 19:39 – Updated: 2026-02-20 16:46Impact
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 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 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.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c 1.18.5"
},
"package": {
"ecosystem": "Go",
"name": "github.com/cilium/cilium"
},
"ranges": [
{
"events": [
{
"introduced": "1.18.0"
},
{
"fixed": "1.18.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-26963"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-19T19:39:01Z",
"nvd_published_at": "2026-02-20T00:16:16Z",
"severity": "MODERATE"
},
"details": "### Impact\n\n[Host Policies](https://docs.cilium.io/en/stable/security/policy/language/#host-policies) will incorrectly permit traffic from Pods on other nodes when all of the following configurations are enabled:\n* [Native Routing](https://docs.cilium.io/en/stable/network/concepts/routing/#native-routing)\n* [WireGuard](https://docs.cilium.io/en/stable/security/policy/language/#host-policies)\n* [Node Encryption](https://docs.cilium.io/en/stable/security/network/encryption-wireguard/#node-to-node-encryption-beta) (beta)\n\nThese options are disabled by default in Cilium.\n\n### Patches\n\nThis issue was fixed by #42892.\n\nThis issue affects:\n\n* Cilium v1.18 between v1.18.0 and v1.18.5 inclusive\n\nThis issue is fixed in:\n\n* Cilium v1.18.6\n\n### Workarounds\n\nThere is currently no officially verified or comprehensive workaround for this issue. The following procedure has been validated strictly within a local \u0027Kind\u0027 environment and has not undergone exhaustive testing across diverse production architectures. Proceed with caution.\n\nTo 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:\n\n```bash\n# IPv4 Traffic\nip rule add iif cilium_wg0 table 300\nip route add default dev cilium_host table 300\n\n# IPv6 Traffic\nip -6 rule add iif cilium_wg0 table 300\nip -6 route add default dev cilium_net table 300\n```\n\n### Acknowledgements\n\nSpecial thanks to @julianwiedmann for reporting the issue and helping with the resolution.\n\n### For more information\n\nIf 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.",
"id": "GHSA-5r23-prx4-mqg3",
"modified": "2026-02-20T16:46:49Z",
"published": "2026-02-19T19:39:01Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/security/advisories/GHSA-5r23-prx4-mqg3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26963"
},
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/pull/42892"
},
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/commit/88e28e1e62c0b1a02c3f0fc22d888ac9eefbe885"
},
{
"type": "PACKAGE",
"url": "https://github.com/cilium/cilium"
},
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/releases/tag/v1.18.6"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.