Gateway API route matching order contradicts specification

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2024-42487: 0.53% estimated exploitation activity in the next 30 days; percentile 45.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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 (HTTPRouteRule, GRPCRouteRule). If 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. Patches This issue was fixed in https://github.com/cilium/cilium/pull/34109. This issue affects: - Cilium v1.15 between v1.15.0 and v1.15.7 inclusive - Cilium v1.16.0 This issue is fixed in: - Cilium v1.15.8 - Cilium v1.16.1 Workarounds There is no workaround for this issue. Acknowledgements The Cilium community…

Published by the source

15 Aug 2024, 21:46 UTC

Last modified by the source

30 Sep 2024, 19:48 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qcm3-7879-xcww

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-42487

Advisory: Gateway API route matching order contradicts specification
IDs: CVE-2024-42487, GHSA-qcm3-7879-xcww
Record: https://patchnext.com/advisories/cve-2024-42487 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cilium/cilium 1.16.1, 1.15.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected >= 1.16.0, <= 1.16.0; >= 1.15.0, < 1.15.8; fixed in 1.15.8, 1.16.1

## Suggested inspection (read-only)
- Go github.com/cilium/cilium: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cilium/cilium.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qcm3-7879-xcww (GitHub-reviewed advisory GHSA-qcm3-7879-xcww lists affected ranges: Go github.com/cilium/cilium >=1.16.0 =1.15.0 <1.15.8)

Commands are suggestions: review each one before running it.