{"id":"CVE-2024-42487","aliases":["BIT-cilium-2024-42487","BIT-cilium-operator-2024-42487","BIT-hubble-relay-2024-42487","EUVD-2024-2632","GHSA-qcm3-7879-xcww","GO-2024-3071"],"status":"published","title":"Cilium's Gateway API route matching order contradicts specification","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","severity":{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00535,"percentile":0.45493,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-113","CWE-436"],"published":"2024-08-15T20:26:53Z","modified":"2026-10-28T02:30:23Z","fixes":[{"ecosystem":"Go","package":"github.com/cilium/cilium","fixed_in":["1.16.1","1.15.8"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"cilium","fixed_in":["1.16.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"cilium-operator","fixed_in":["1.16.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-relay","fixed_in":["1.16.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.16.0"},{"last_affected":"1.16.0"},{"fixed":"1.16.1"}]}],"versions":["1.16.0"]},{"source":"ghsa","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.0"},{"fixed":"1.15.8"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.15.0"},{"fixed":"1.16.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium-operator","ranges":[{"type":"SEMVER","events":[{"introduced":"1.15.4"},{"fixed":"1.16.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-relay","ranges":[{"type":"SEMVER","events":[{"introduced":"1.15.0"},{"fixed":"1.16.1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.16.0"},{"fixed":"1.16.1"}]}],"versions":["1.16.0"]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.15.0"},{"fixed":"1.15.8"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.15.0"},{"fixed":"1.15.8"},{"introduced":"1.16.0"},{"fixed":"1.16.1"}]}]}],"products":[{"vendor":"cilium","product":"cilium"}],"references":[{"url":"https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory","web"]},{"url":"https://github.com/cilium/cilium/pull/34109","tags":["x_refsource_MISC","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a","tags":["x_refsource_MISC","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42487","tags":["web","advisory"]},{"url":"https://github.com/cilium/cilium/commit/d88772b9c29e370becbc4547cada6711d51edcde","tags":["web","fix"]},{"url":"https://github.com/cilium/cilium/commit/fe42273566a943a0f3174c87b23a195c856b51d6","tags":["web","fix"]},{"url":"https://github.com/advisories/GHSA-qcm3-7879-xcww"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/42xxx/CVE-2024-42487.json","tags":["advisory"]},{"url":"https://github.com/cilium/cilium","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2024-42487","title":"Cilium's Gateway API route matching order contradicts specification","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-15T20:26:53.455Z","modified":"2024-08-15T20:46:34.91Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-113"],"updated_at":"2026-11-02T14:34:03.00063Z"}],"euvd":[{"id":"EUVD-2024-2632","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-15T20:26:53Z","modified":"2024-08-15T20:46:34Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-03T00:56:16.665209Z"}],"ghsa":[{"id":"GHSA-qcm3-7879-xcww","title":"Gateway API route matching order contradicts specification","description":"### Impact\n\nGateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched ([HTTPRouteRule](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule), [GRPCRouteRule](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1.GRPCRouteRule)).\n\nIf users create Gateway API resources that use both request headers and request methods in order to route to different destinations, then traffic may be delivered to the incorrect backend. If the backend does not have Network Policy restricting acceptable traffic to receive, then requests may access information that you did not intend for them to access.\n\n### Patches\n\nThis issue was fixed in https://github.com/cilium/cilium/pull/34109.\n\nThis issue affects:\n- Cilium v1.15 between v1.15.0 and v1.15.7 inclusive\n- Cilium v1.16.0\n\nThis issue is fixed in:\n- Cilium v1.15.8\n- Cilium v1.16.1\n\n### Workarounds\n\nThere is no workaround for this issue.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @sayboras for remediating this issue.\n\n### Further 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\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](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.\n","status":"published","published":"2024-08-15T21:46:46Z","modified":"2024-09-30T19:48:19Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-113","CWE-436"],"updated_at":"2026-11-02T14:38:07.852618Z"}],"nvd":[{"id":"CVE-2024-42487","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-15T21:15:16.997Z","modified":"2026-06-17T07:49:32.767Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-113","CWE-436"],"updated_at":"2026-11-02T14:10:19.135392Z"}],"osv":[{"id":"CVE-2024-42487","title":"Cilium's Gateway API route matching order contradicts specification","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-15T20:26:53.455Z","modified":"2026-10-28T02:30:23.924869633Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-113"],"updated_at":"2026-11-02T15:44:42.322107Z"},{"id":"GHSA-qcm3-7879-xcww","title":"Gateway API route matching order contradicts specification","description":"### Impact\n\nGateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched ([HTTPRouteRule](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule), [GRPCRouteRule](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1.GRPCRouteRule)).\n\nIf users create Gateway API resources that use both request headers and request methods in order to route to different destinations, then traffic may be delivered to the incorrect backend. If the backend does not have Network Policy restricting acceptable traffic to receive, then requests may access information that you did not intend for them to access.\n\n### Patches\n\nThis issue was fixed in https://github.com/cilium/cilium/pull/34109.\n\nThis issue affects:\n- Cilium v1.15 between v1.15.0 and v1.15.7 inclusive\n- Cilium v1.16.0\n\nThis issue is fixed in:\n- Cilium v1.15.8\n- Cilium v1.16.1\n\n### Workarounds\n\nThere is no workaround for this issue.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @sayboras for remediating this issue.\n\n### Further 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\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](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.\n","status":"published","published":"2024-08-15T21:46:46Z","modified":"2026-09-10T03:50:18.772773817Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-113","CWE-436"],"updated_at":"2026-11-02T15:46:54.40888Z"},{"id":"BIT-cilium-2024-42487","title":"Cilium's Gateway API route matching order contradicts specification","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-17T07:16:43.256Z","modified":"2026-09-08T08:45:55.969832045Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-cilium-operator-2024-42487","title":"Cilium's Gateway API route matching order contradicts specification","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-17T07:16:43.549Z","modified":"2026-09-08T08:45:17.34627213Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-hubble-relay-2024-42487","title":"Cilium's Gateway API route matching order contradicts specification","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.","status":"published","published":"2024-08-17T07:20:18.655Z","modified":"2026-09-08T08:48:23.058714293Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"GO-2024-3071","title":"Gateway API route matching order contradicts specification in github.com/cilium/cilium","description":"Gateway API route matching order contradicts specification in github.com/cilium/cilium","status":"published","published":"2024-08-16T17:28:56Z","modified":"2026-02-04T02:38:24.475583Z","updated_at":"2026-11-02T15:47:01.453823Z"}]}}