Answer in brief
CVE-2023-29002 records a High severity (CVSS 7.2) vulnerability in Debug mode leaks confidential data in Cilium. The current sources do not mark it as known exploited. The current feed maps github.com/cilium/cilium (go), github.com/cilium/cilium (go), github.com/cilium/cilium (go), github.com/cilium/cilium (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps github.com/cilium/cilium (go), github.com/cilium/cilium (go), github.com/cilium/cilium (go), github.com/cilium/cilium (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/cilium/ciliumgo | >=1.7.0 | Not reported |
| github.com/cilium/ciliumgo | >=1.11.0 <1.11.16 | 1.11.16 |
| github.com/cilium/ciliumgo | >=1.12.0 <1.12.9 | 1.12.9 |
| github.com/cilium/ciliumgo | >=1.13.0 <1.13.2 | 1.13.2 |
Published upstream
Apr 19, 2023
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
### 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](https://docs.cilium.io/en/latest/community/community/#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: [[email protected]](mailto:[email protected]) - 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.
Quoted source text, attributed separately from HOL analysis.