CVE-2024-42486: Cilium leaks information via incorrect ReferenceGrant update logic in Gateway API
Impact Due to ReferenceGrant changes not being immediately propagated in Cilium's GatewayAPI controller, Gateway resources are able to access secrets in other namespaces after the associated ReferenceGrant has been revoked. This can lead to Gateways continuing to establish sessions using secrets that they should no longer have access to. Patches This issue was resolved in https://github.com/cilium/cilium/pull/34032.
Published Aug 16, 2024
Affected packages
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- = 1.16.0
- Fixed in
- 1.16.1
- Check
go list -m github.com/cilium/cilium
github.com/cilium/cilium
- Ecosystem
- Go
- Affected
- >= 1.15.0, < 1.15.8
- Fixed in
- 1.15.8
- Check
go list -m github.com/cilium/cilium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Due to ReferenceGrant changes not being immediately propagated in Cilium's GatewayAPI controller, Gateway resources are able to access secrets in other namespaces after the associated ReferenceGrant has been revoked. This can lead to Gateways continuing to establish sessions using secrets that they should no longer have access to.
Patches
This issue was resolved in https://github.com/cilium/cilium/pull/34032.
This issue affects:
- Cilium v1.15 between v1.15.0 and v1.15.7 inclusive
- Cilium v1.16.0
This issue has been patched in:
- Cilium v1.15.8
- Cilium v1.16.1
Workarounds
Any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster.
Acknowledgements
The Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @sayboras for resolving this issue.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
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]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
Credited to sayboras.
References
- https://github.com/cilium/cilium/security/advisories/GHSA-vwf8-q6fw-4wcm
- https://nvd.nist.gov/vuln/detail/CVE-2024-42486
- https://github.com/cilium/cilium/pull/34032
- https://github.com/cilium/cilium/commit/414a96b53d51ef6e6645c44426e26bc8e7c7c059
- https://github.com/cilium/cilium/commit/92c110e58a7be6586819dd51fb0f6ee1ec4be8f8
- https://github.com/cilium/cilium/commit/ed3dfa0aab8b80f7e841a6d49d2a990ac2dca053
- https://github.com/advisories/GHSA-vwf8-q6fw-4wcm
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
