CriticalGHSA-3fcv-jvfp-m4q9BIT-cilium-2026-49445BIT-cilium-operator-2026-49445BIT-hubble-relay-2026-49445CVE-2026-49445

Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access

Published 6 Jul 2026 · Updated 20 Jul 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.19.0 <1.19.2
Fixed in
1.19.2
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.19.2
Affected
>=1.18.0 <1.18.8
Fixed in
1.18.8
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.18.8
Affected
<1.17.14
Fixed in
1.17.14
Update to the fixed version for your release line, for example:go get github.com/cilium/cilium@v1.17.14

Details

Impact

When Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as:

  • Exposing TLS secrets
  • Disrupting traffic in the cluster
  • Terminating the Envoy process

This issue affects both the embedded and standalone Envoy deployment models.

Patches

This issue affects:

  • Cilium v1.19 between v1.19.0 and v1.19.1 inclusive
  • Cilium v1.18 between v1.18.0 and v1.18.7 inclusive
  • All versions of Cilium prior to v1.17.14

This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in:

  • Cilium v1.19.2
  • Cilium v1.18.8
  • Cilium v1.17.14

Workarounds

There is no known workaround to this issue.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to moemen for reporting the issue and 0xch4z for their work on triaging and remediating this issue.

For more information

If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/).

If anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.

Is GHSA-3fcv-jvfp-m4q9 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-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces in github.com/cilium/cilium · 1 Oct 2026
  • MediumCVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces · 24 Sept 2026
  • 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-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
All 75 advisories for github.com/cilium/cilium

References

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