Affected by GO-2025-3416
and 6 other vulnerabilities
GO-2025-3416: Cilium has an information leakage via insecure default Hubble UI CORS header in github.com/cilium/cilium
GO-2025-3635: In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters in github.com/cilium/cilium
GO-2025-4167: Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic in Ciliumgithub.com/cilium/cilium
GO-2026-4856: Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic in github.com/cilium/cilium
GO-2026-5400: Cillium exposes sensitive information included in the cilium-bugtool debug archive in github.com/cilium/cilium
GO-2026-5905: Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access in github.com/cilium/cilium
GO-2026-5914: CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation in github.com/cilium/cilium
IncTimer should be the preferred mechanism over
calling `time.After` when wanting an `After`-like
function in a loop. This prevents memory build up
as the `time.After` method creates a new timer
instance every time it is called, and it is not
garbage collected until after it fires. Conversely,
IncTimer only uses one timer and correctly stops
the timer, clears its channel, and resets it
everytime that `After` is called.
New creates a new IncTimer and a done function.
IncTimer only uses one timer and correctly stops
the timer, clears the channel, and resets it every
time the `After` function is called.
WARNING: Concurrent use is not expected. The use
of this timer should be for only one goroutine.
Affected by 
Documentation
¶
Source Files