vulnerability / NVI-00013197 / Revision 4
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
GitHub lists this reviewed advisory for github.com/cilium/cilium, github.com/cilium/ciliumCilium, github.com/cilium/cilium. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
5.9 medium
GitHub source severity; exploitability and local consequence require separate evidence.
As of · GitHub Advisory Database
0.176%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.07116. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
github.com/cilium/cilium
source listed< 1.17.17
### Impact In Cilium clusters using Gateway API, users with permissions to create or update namespaced HTTPRoutes can mirror HTTP traffic to any Service in any namespace, bypassing the ReferenceGrant authorization mechanism. Gateway API functionality is disabled by default. ### Patches This issue affects: * Cilium v1.19 from v1.19.0 to v1.19.4 inclusive * Cilium v1.18 from v1.18.0 to v1.18.10 inclusive * All versions of Cilium before v1.17.17 This issue is patched in: * Cilium v1.19.5 * Cilium v1.18.11 * Cilium v1.17.17 ### Workarounds There is no workaround to this issue. Users of this feature who are unable to upgrade can mitigate the risk by ensuring that RBAC permissions to create `HTTPRoute` objects are only granted to cluster admins. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @galanko for reporting the issue and @mhofstetter for their work on triaging and remediating this issue. ### For more information If you have any questions or comments about this advisory, please reach out on [Slack](htt
github.com/cilium/ciliumCilium
source listed>= 1.18.0, < 1.18.11
### Impact In Cilium clusters using Gateway API, users with permissions to create or update namespaced HTTPRoutes can mirror HTTP traffic to any Service in any namespace, bypassing the ReferenceGrant authorization mechanism. Gateway API functionality is disabled by default. ### Patches This issue affects: * Cilium v1.19 from v1.19.0 to v1.19.4 inclusive * Cilium v1.18 from v1.18.0 to v1.18.10 inclusive * All versions of Cilium before v1.17.17 This issue is patched in: * Cilium v1.19.5 * Cilium v1.18.11 * Cilium v1.17.17 ### Workarounds There is no workaround to this issue. Users of this feature who are unable to upgrade can mitigate the risk by ensuring that RBAC permissions to create `HTTPRoute` objects are only granted to cluster admins. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @galanko for reporting the issue and @mhofstetter for their work on triaging and remediating this issue. ### For more information If you have any questions or comments about this advisory, please reach out on [Slack](htt
github.com/cilium/cilium
source listed>= 1.19.0, < 1.19.5
### Impact In Cilium clusters using Gateway API, users with permissions to create or update namespaced HTTPRoutes can mirror HTTP traffic to any Service in any namespace, bypassing the ReferenceGrant authorization mechanism. Gateway API functionality is disabled by default. ### Patches This issue affects: * Cilium v1.19 from v1.19.0 to v1.19.4 inclusive * Cilium v1.18 from v1.18.0 to v1.18.10 inclusive * All versions of Cilium before v1.17.17 This issue is patched in: * Cilium v1.19.5 * Cilium v1.18.11 * Cilium v1.17.17 ### Workarounds There is no workaround to this issue. Users of this feature who are unable to upgrade can mitigate the risk by ensuring that RBAC permissions to create `HTTPRoute` objects are only granted to cluster admins. ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @galanko for reporting the issue and @mhofstetter for their work on triaging and remediating this issue. ### For more information If you have any questions or comments about this advisory, please reach out on [Slack](htt
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-w7c2-w76w-5hmj ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
- CVE-2026-56742 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 4 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 3 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.