{"id":"CVE-2023-27594","aliases":["BIT-cilium-2023-27594","BIT-cilium-operator-2023-27594","BIT-cilium-proxy-2023-27594","BIT-hubble-2023-27594","BIT-hubble-relay-2023-27594","BIT-hubble-ui-2023-27594","BIT-hubble-ui-backend-2023-27594","EUVD-2023-0945","GHSA-8fg8-jh2h-f2hc","GO-2023-1643"],"status":"published","title":"Cilium vulnerable to potential network policy bypass when routing IPv6 traffic","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","severity":{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00552,"percentile":0.46655,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-285","CWE-863"],"published":"2023-03-17T18:22:19Z","modified":"2026-10-28T02:30:23Z","fixes":[{"ecosystem":"Go","package":"github.com/cilium/cilium","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"cilium","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"cilium-operator","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"cilium-proxy","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-relay","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-ui","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-ui-backend","fixed_in":["1.11.15","1.12.8","1.13.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.11.15"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.12.0"},{"fixed":"1.12.8"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium-operator","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium-proxy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-relay","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-ui","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-ui-backend","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.12.0"},{"fixed":"1.12.8"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.15"},{"introduced":"1.12.0"},{"fixed":"1.12.8"},{"introduced":"1.13.0"},{"fixed":"1.13.1"}]}]}],"products":[{"vendor":"cilium","product":"cilium"}],"references":[{"url":"https://github.com/cilium/cilium/security/advisories/GHSA-8fg8-jh2h-f2hc","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/cilium/cilium/releases/tag/v1.11.15","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/cilium/cilium/releases/tag/v1.12.8","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/cilium/cilium/releases/tag/v1.13.1","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-27594","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-8fg8-jh2h-f2hc"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/27xxx/CVE-2023-27594.json","tags":["advisory"]},{"url":"https://github.com/cilium/cilium","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2023-27594","title":"Cilium vulnerable to potential network policy bypass when routing IPv6 traffic ","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2023-03-17T19:56:43.687Z","modified":"2025-02-25T14:53:31.518Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-285"],"updated_at":"2026-11-02T14:35:26.261013Z"}],"euvd":[{"id":"EUVD-2023-0945","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2023-03-17T19:56:43Z","modified":"2025-02-25T14:53:31Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T20:53:24.646946Z"}],"ghsa":[{"id":"GHSA-8fg8-jh2h-f2hc","title":"Potential network policy bypass when routing IPv6 traffic ","description":"## Impact\n\nUnder specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled. Only IPv6 traffic is impacted by this vulnerability.\n\nThis issue only manifests when:\n* Cilium is routing IPv6 traffic, and\n* Kube-proxy is used for service handling, and\n* NodePorts are used to route traffic to pods.\n\nIPv6 is disabled by default. Cilium's kube-proxy replacement feature is not affected by this vulnerability.\n\n## Patches\n\nThe problem has been fixed and is available on versions \u003e=1.11.15, \u003e=1.12.8, \u003e=1.13.1\n\n## Workarounds\n\nDisable IPv6 routing (IPv6 is disabled by default).\n\n## Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Yusuke Suzuki for both highlighting and fixing the issue.\n\n## For more information\n\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nAs 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.","status":"published","published":"2023-03-17T18:22:19Z","modified":"2023-03-24T21:41:28Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-285","CWE-863"],"updated_at":"2026-11-02T14:36:48.905887Z"}],"nvd":[{"id":"CVE-2023-27594","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2023-03-17T20:15:13.583Z","modified":"2026-06-17T05:45:32.733Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high","assessor":"primary"}],"cwes":["CWE-285","CWE-863"],"updated_at":"2026-11-02T14:07:49.031498Z"}],"osv":[{"id":"CVE-2023-27594","title":"Cilium vulnerable to potential network policy bypass when routing IPv6 traffic ","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2023-03-17T19:56:43.687Z","modified":"2026-10-28T02:30:23.186691525Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-285"],"updated_at":"2026-11-02T15:44:31.135751Z"},{"id":"GHSA-8fg8-jh2h-f2hc","title":"Potential network policy bypass when routing IPv6 traffic ","description":"## Impact\n\nUnder specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled. Only IPv6 traffic is impacted by this vulnerability.\n\nThis issue only manifests when:\n* Cilium is routing IPv6 traffic, and\n* Kube-proxy is used for service handling, and\n* NodePorts are used to route traffic to pods.\n\nIPv6 is disabled by default. Cilium's kube-proxy replacement feature is not affected by this vulnerability.\n\n## Patches\n\nThe problem has been fixed and is available on versions \u003e=1.11.15, \u003e=1.12.8, \u003e=1.13.1\n\n## Workarounds\n\nDisable IPv6 routing (IPv6 is disabled by default).\n\n## Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Yusuke Suzuki for both highlighting and fixing the issue.\n\n## For more information\n\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nAs 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.","status":"published","published":"2023-03-17T18:22:19Z","modified":"2026-09-10T03:49:52.8879096Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-285","CWE-863"],"updated_at":"2026-11-02T15:46:42.437513Z"},{"id":"BIT-cilium-2023-27594","title":"Cilium vulnerable to potential network policy bypass when routing IPv6 traffic ","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-05-15T12:08:16.078Z","modified":"2026-09-08T08:45:53.651513233Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-cilium-operator-2023-27594","title":"Cilium vulnerable to potential network policy bypass when routing IPv6 traffic ","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-05-15T12:08:08.478Z","modified":"2026-09-08T08:45:54.986644393Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-cilium-proxy-2023-27594","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-07-01T11:13:29.794Z","modified":"2024-08-20T20:59:05.679993Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-hubble-2023-27594","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-06-04T09:45:27.802Z","modified":"2024-08-20T20:59:05.679993Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"BIT-hubble-relay-2023-27594","title":"Cilium vulnerable to potential network policy bypass when routing IPv6 traffic ","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.\n\nThis issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.\n\nThe problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-05-24T19:23:31.489Z","modified":"2026-09-08T08:48:23.086019159Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"BIT-hubble-ui-2023-27594","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-07-01T11:18:35.198Z","modified":"2024-08-20T20:59:05.679993Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"BIT-hubble-ui-backend-2023-27594","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, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.","status":"published","published":"2024-07-01T11:18:38.397Z","modified":"2024-08-20T20:59:05.679993Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"GO-2023-1643","title":"Potential network policy bypass when routing IPv6 traffic in github.com/cilium/cilium","description":"Potential network policy bypass when routing IPv6 traffic in github.com/cilium/cilium","status":"published","published":"2024-08-20T20:29:17Z","modified":"2026-02-04T04:00:35.112339Z","updated_at":"2026-11-02T15:47:01.185262Z"}]}}