Debug mode leaks confidential data in Cilium
Published 19 Apr 2023 · Updated 10 Sept 2026
Is your project on an affected github.com/cilium/cilium?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=1.7.0 <=1.10.0
- Fixed in
- No fix released
- Affected
- >=1.11.0 <1.11.16
- Fixed in
- 1.11.16
go get github.com/cilium/cilium@v1.11.16- Affected
- >=1.12.0 <1.12.9
- Fixed in
- 1.12.9
go get github.com/cilium/cilium@v1.12.9- Affected
- >=1.13.0 <1.13.2
- Fixed in
- 1.13.2
go get github.com/cilium/cilium@v1.13.2Details
Impact
When run in debug mode, Cilium may log sensitive information.
In particular, Cilium running in debug mode will log the values of headers if they match HTTP network policy rules. This issue affects Cilium versions:
- 1.7.* to 1.10.* inclusive
- 1.11.* before 1.11.16
- 1.12.* before 1.12.9
- 1.13.* before 1.13.2
In addition, Cilium 1.12.* before 1.12.9 and 1.13.* before 1.13.2., when running in debug mode, might log secrets used by the Cilium agent. This includes TLS private keys for Ingress and GatewayAPI resources, depending on the configuration of the affected cluster. Output of the confidential data would occur at Cilium agent restart, when the secrets are modified, and on creation of Ingress or GatewayAPI resources.
Patches
This vulnerability is fixed in Cilium releases 1.11.16, 1.12.9, and 1.13.2.
Workarounds
Disable debug mode.
Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @meyskens for investigating and fixing the issue.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
Is GHSA-pg5p-wwp8-97g8 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-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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.