Debug mode leaks confidential data in Cilium

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.2 · CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2023-29002: 0.20% estimated exploitation activity in the next 30 days; percentile 9.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

19 Apr 2023, 18:16 UTC

Last modified by the source

12 Nov 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pg5p-wwp8-97g8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-29002

Advisory: Debug mode leaks confidential data in Cilium
IDs: CVE-2023-29002, GHSA-pg5p-wwp8-97g8
Record: https://patchnext.com/advisories/cve-2023-29002 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/cilium/cilium 1.13.2, 1.12.9, 1.11.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected >= 1.7.0, <= 1.10.0; >= 1.11.0, < 1.11.16; >= 1.12.0, < 1.12.9; >= 1.13.0, < 1.13.2; fixed in 1.12.9, 1.11.16, 1.13.2

## Suggested inspection (read-only)
- Go github.com/cilium/cilium: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cilium/cilium.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pg5p-wwp8-97g8 (GitHub-reviewed advisory GHSA-pg5p-wwp8-97g8 lists affected ranges: Go github.com/cilium/cilium >=1.7.0 =1.11.0 =1.12.0 =1.13.0 <1.13.2)

Commands are suggestions: review each one before running it.