CVE-2026-53935: CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
Impact Users with the ability to create CiliumLocalRedirectPolicies can specify arbitrary ClusterIPs via addressMatcher, which enables hijacking traffic to Services in any namespace, bypassing the namespace-scoping guarantees enforced by serviceMatcher. In addition, deleting such a policy can corrupt Cilium's internal service state, causing service translation to stop working entirely for the affected Service.
Published Jul 6, 2026
Affected packages
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.19.0, < 1.19.4
- Fixed in
- 1.19.4
- Check
go list -m github.com/cilium/cilium
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.18.2, < 1.18.10
- Fixed in
- 1.18.10
- Check
go list -m github.com/cilium/cilium
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- < 1.17.16
- Fixed in
- 1.17.16
- Check
go list -m github.com/cilium/cilium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Users with the ability to create CiliumLocalRedirectPolicies can specify arbitrary ClusterIPs via addressMatcher, which enables hijacking traffic to Services in any namespace, bypassing the namespace-scoping guarantees enforced by serviceMatcher.
In addition, deleting such a policy can corrupt Cilium's internal service state, causing service translation to stop working entirely for the affected Service.
Patches
This issue affects:
- Cilium v1.19.0 to v1.19.3 inclusive (fixed in PR #45584)
- Cilium v1.18.2 to v1.18.9 inclusive (fixed in PR #45585)
- All versions of Cilium prior to v1.17.16 (fixed in PR #45412)
This issue has been patched in:
- Cilium v1.19.4
- Cilium v1.18.10
- Cilium v1.17.16
Workarounds
There is no workaround to this issue.
Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @ysksuzuki for investigating and fixing the issue.
For more information
If there are any questions or comments about this advisory, please reach out on Slack.
To report potential vulnerabilities affecting Cilium, it strongly is encouraged to report them through the security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and reports will be treated as a top priority.
References
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-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, 2026CVE-2026-26963
Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled
medium6.1Feb 19, 2026
