MediumGHSA-w7c2-w76w-5hmjBIT-cilium-2026-56742BIT-cilium-operator-2026-56742BIT-hubble-relay-2026-56742CVE-2026-56742

Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces

Published 24 Sept 2026 · Updated 1 Oct 2026

Is your project on an affected github.com/cilium/cilium?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<1.17.17
Fixed in
1.17.17
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.17.17
Affected
>=1.18.0 <1.18.11
Fixed in
1.18.11
Update to the fixed version for your release line, for example:go get github.com/cilium/ciliumCilium@v1.18.11
Affected
>=1.19.0 <1.19.5
Fixed in
1.19.5
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.19.5

Details

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.

If 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.

Is GHSA-w7c2-w76w-5hmj in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cilium/cilium, and gives you the command that fixes it.

More advisories for github.com/cilium/cilium

  • LowCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match in github.com/cilium/cilium · 10 Sept 2026
  • MediumCVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match · 3 Sept 2026
  • LowCVE-2026-49445Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access in github.com/cilium/cilium · 7 Jul 2026
  • LowCVE-2026-53935CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation in github.com/cilium/cilium · 7 Jul 2026
  • MediumCVE-2026-53935CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation · 6 Jul 2026
  • CriticalCVE-2026-49445Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access · 6 Jul 2026
All 75 advisories for github.com/cilium/cilium

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.