Affected by GO-2025-3415
and 5 other vulnerabilities
GO-2025-3415: DoS in Cilium agent DNS proxy from crafted DNS responses in github.com/cilium/cilium
GO-2025-3416: Cilium has an information leakage via insecure default Hubble UI CORS header in github.com/cilium/cilium
GO-2025-3560: Cilium East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers in github.com/cilium/cilium
GO-2025-3561: Cilium node based network policies may incorrectly allow workload traffic 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
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