# Cilium v1.19.11

2026-11-17 · [Original release notes](https://github.com/cilium/cilium/releases/tag/v1.19.11) · [Full summary](https://ratatosk.io/en/releases/cilium/v1.19.11)

Security 2 · Breaking changes 2 · Important fixes 8 · Enhancements 1 · Dependency updates 21 · Other changes 21

## Security (2)

### [Security status unclear] Egress wildcard allow in combined `toServices` and `toPorts` rules fixed

- Affects: egress policies combining `toServices` with `toPorts`

When the referenced Service was missing or selector-less with no backends, these rules allowed traffic to any destination on the specified ports. That traffic is now denied until the Service exists and, if selector-less, has backends.

> * Fix egress policy rules that combine `toServices` with `toPorts` allowing traffic to any destination on those ports when the referenced Service doesn't exist or is selector-less with no backends. (Backport PR cilium/cilium#49637, Upstream PR cilium/cilium#49430, @christarazi)

### Hubble URL-query redaction fixed for unparseable Envoy access-log URLs

- Affects: Envoy access-log flows with `--hubble-redact-http-urlquery` enabled

When an access-log URL failed to parse, its query could remain in the exported Hubble flow URL. The fallback now separates the query and fragment from the path, allowing URL-query redaction to remove the query.

> * Fix HTTP URL query not being redacted in Hubble flows when the Envoy access log URL fails to parse. (Backport PR cilium/cilium#49805, Upstream PR cilium/cilium#49427, @sage-mode-hunter)

## Breaking changes (2)

### DNS proxy port-registration failures now terminate the agent

- Affects: DNS proxy listener-port registration

Previously, a registration failure during agent startup logged a warning and startup continued. Now the failure is logged at error level before the agent terminates.

Evidence: “If DNS proxy port registration fails, return the error to Hive's job runner, which logs it at error level and terminates the agent. Previously, this failure logged a warning and startup continued.” https://github.com/cilium/cilium/pull/49540

> * Fix agent bootstrap to order endpoint regeneration after DNS proxy initialization to prevent proxy port race. (Backport PR cilium/cilium#49805, Upstream PR cilium/cilium#49540, @jrajahalme)

### Empty `redirectBackend.toPorts` arrays rejected in CiliumLocalRedirectPolicy

- Affects: CiliumLocalRedirectPolicy resources with an empty `redirectBackend.toPorts` array

Previously, applying one of these policies could panic the agent. The CRD now rejects the empty array, and the parser fails the policy instead of allowing the panic.

Evidence: “Cilium LocalRedirectPolicy CRD requires spec.redirectBackend.toPorts to be specified, but it doesn't enforce a minimum number of elements. This means you can apply a CLRP with an empty redirectBackend.toPorts array, leading to a panic in the agent, because the size of the array isn't validated before access.” https://github.com/cilium/cilium/pull/48491

> * Fix panic in agent when CiliumLocalRedirectPolicy `redirectBackend.toPorts` is declared as an empty array. The agent will now reject such a policy. (Backport PR cilium/cilium#49923, Upstream PR cilium/cilium#48491, @ajmmm)

## Important fixes (8)

### Tunnel-traffic `NOTRACK` rules exclude transit traffic

- Affects: datapath iptables rules for tunnel traffic (`NOTRACK`) (Inferred)

Previously, matching tunnel UDP destination ports alone let some legitimate transit packets bypass the node’s normal packet path. The rules now match local node addresses, so transit traffic not addressed to the node is handled as non-local traffic.

> * datapath/iptables: scope iptables rules for tunnel traffic (NOTRACK) to local node addresses by matching addrtype (Backport PR cilium/cilium#50041, Upstream PR cilium/cilium#49266, @bersoare)

### [Silent failure] Node handler honors `--use-cilium-internal-ip-for-ipsec`

- Affects: setups using `--use-cilium-internal-ip-for-ipsec` with subnet encryption

Before this fix, with subnet encryption enabled on multi-interface nodes where Kubernetes InternalIP was not the first address on the first native device, the flag was silently ignored and the agent used `odeInternalIPs`, causing `XfrmInNoStates` drops.

> * Use the real IPsec config in nodeHandler, which restores the `--use-cilium-internal-ip-for-ipsec` behavior (Backport PR cilium/cilium#49839, Upstream PR cilium/cilium#49827, @vakalapa)

### MCS-API EndpointSlice mirror crash fixed

- Affects: MCS-API EndpointSlice mirroring

When a derived EndpointSlice lacked `ownerReferences`, the check could index `OwnerReferences[0]` and crash the operator.

> * clustermesh: fix ownerReferences check in MCS-API EndpointSlice mirror (cilium/cilium#50010, @brb)

### Endpoint regeneration rollback state now uses the final return error

- Affects: endpoint BPF regeneration (Inferred)

> * endpoint: use final regeneration error to resolve rollback state (Backport PR cilium/cilium#49680, Upstream PR cilium/cilium#49471, @jrajahalme)

### Restored endpoints published after DNS proxy initialization

- Affects: DNS proxy functionality (Inferred)

During agent bootstrap, endpoint regeneration could create DNS redirects before the DNS proxy registered its listener port, racing with static proxy-port setup. Restored endpoints are now published only after DNS proxy initialization completes.

> * Fix agent bootstrap to order endpoint regeneration after DNS proxy initialization to prevent proxy port race. (Backport PR cilium/cilium#49805, Upstream PR cilium/cilium#49540, @jrajahalme)

### BPF masquerade hairpin SNAT fix for kube-proxy access

- Affects: BPF masquerade with kube-proxy and `KPR` disabled

Pods could not reach `eTP=Local` LoadBalancer VIPs or NodePorts on their own node via kube-proxy because reply traffic bypassed the stack and DNAT was not reversed. The hairpin SNAT rule now enables that access; backends see the `cilium_host` address, while identity-based policy still applies.

> * Fix pods failing to reach LoadBalancer VIPs and NodePorts of eTP=Local services via kube-proxy with BPF masquerade and KPR disabled. (Backport PR cilium/cilium#49923, Upstream PR cilium/cilium#49066, @maxskokov)

### Benign leader-election lease conflicts logged at info

- Affects: Cilium deployments using operator leader election

During a rolling upgrade, old and new operator leaders can briefly contend for the same lease, causing a benign `409` conflict that was logged at error level and could trip CI's `check-log-errors` check. Genuine lease-update failures, such as control-plane overload, remain at error level.

> * logging: Downgrade leader election lease conflict to info (Backport PR cilium/cilium#49976, Upstream PR cilium/cilium#46313, @christarazi)

### Stale ingress connection-tracking redirects fixed

- Affects: ingress proxying for L7 rules

With legacy host routing, entries left open until connection-tracking garbage collection could be reused by a new connection with the same tuple; a stale `proxy_redirect` sent the pod’s SYN-ACK to a proxy with no socket, hanging the handshake. The entry is now recreated when its `proxy_redirect` value differs from the current verdict.

> * bpf: Recreate ingress CT entry if proxy_redirect is stale (Backport PR cilium/cilium#50041, Upstream PR cilium/cilium#49592, @christarazi)

## Enhancements (1)

- Five load-balancer ID allocator metrics added

## Dependency updates (21)

### `github.com/go-jose/go-jose/v4` updated to v4.1.6

- [GHSA-mgcc-cww5-fp2q](https://github.com/advisories/GHSA-mgcc-cww5-fp2q)

> * chore(deps): update module github.com/go-jose/go-jose/v4 to v4.1.6 [security] (v1.19) (cilium/cilium#49657, @cilium-renovate[bot])

### `github.com/gopacket/gopacket` updated to v1.7.2

- [CVE-2026-119299](https://www.cve.org/CVERecord?id=CVE-2026-119299), [GHSA-358w-w75h-x6rx](https://github.com/advisories/GHSA-358w-w75h-x6rx)

Crafted SCTP segments could trigger out-of-bounds panics in the chunk sub-decoder in v1.7.1; the advisory does not affect v1.7.2.

> * fix(deps): update module github.com/gopacket/gopacket to v1.7.2 [security] (v1.19) (cilium/cilium#49953, @cilium-renovate[bot])

### `golang.org/x/crypto` updated to v0.59.0

This update is marked as security-related.

> * fix(deps): update module golang.org/x/crypto to v0.59.0 [security] (v1.19) (cilium/cilium#49972, @cilium-renovate[bot])

### `golang.org/x/net` updated to v0.62.0

> * fix(deps): update module golang.org/x/net to v0.62.0 [security] (v1.19) (cilium/cilium#49679, @cilium-renovate[bot])

### Security updates updated to `v1.47.0`

> * fix(deps): update security updates to v1.47.0 [security] (v1.19) (cilium/cilium#50019, @cilium-renovate[bot])

16 more, none mentioning security

- `* chore(deps): update all-dependencies (v1.19) (cilium/cilium#49439, @cilium-renovate[bot])`
- `* chore(deps): update all-dependencies (v1.19) (cilium/cilium#49901, @cilium-renovate[bot])`
- `* chore(deps): update all-dependencies (v1.19) (cilium/cilium#50032, @cilium-renovate[bot])`
- `* chore(deps): update auto-merge-trusted-deps (v1.19) (cilium/cilium#49599, @cilium-renovate[bot])`
- `* chore(deps): update auto-merge-trusted-deps (v1.19) (cilium/cilium#49697, @cilium-renovate[bot])`
- `* chore(deps): update auto-merge-trusted-deps (v1.19) (cilium/cilium#49902, @cilium-renovate[bot])`
- `* chore(deps): update auto-merge-trusted-deps (v1.19) (cilium/cilium#50025, @cilium-renovate[bot])`
- `* chore(deps): update dependency cilium/cilium-cli to v0.20.2 (v1.19) (cilium/cilium#49918, @cilium-renovate[bot])`
- `* chore(deps): update dependency cilium/cilium-cli to v0.20.3 (v1.19) (cilium/cilium#49998, @cilium-renovate[bot])`
- `* chore(deps): update dependency cilium/little-vm-helper to v0.0.33 (v1.19) (cilium/cilium#49685, @cilium-renovate[bot])`
- `* chore(deps): update gcr.io/distroless/static:nonroot docker digest to 25ac8f0 (v1.19) (cilium/cilium#49749, @cilium-renovate[bot])`
- `* chore(deps): update quay.io/cilium/image-tester docker tag to v1793531520 (v1.19) (cilium/cilium#49757, @cilium-renovate[bot])`
- `* chore(deps): update stable lvh-images (v1.19) (patch) (cilium/cilium#49155, @cilium-renovate[bot])`
- `* fix(deps): update k8s.io patch updates stable to v0.35.10 (v1.19) (cilium/cilium#49900, @cilium-renovate[bot])`
- `* fix(deps): update k8s.io/utils digest to ca04ba5 (v1.19) (cilium/cilium#49750, @cilium-renovate[bot])`
- `* fix(deps): update module k8s.io/apimachinery to v0.35.10 (v1.19) (cilium/cilium#49760, @cilium-renovate[bot])`

## Other changes (21)

- CI workflow maintenance updates
- Renovate auto-approval limited to trusted PRs
- Base-image and docs-builder fallback checkout ref changed to `github.sha`
- Verifier complexity test parses stack depth beyond net-next
- Smoke conformance workflows check out the pull request Helm chart by SHA
- AKS CI setup allows GitHub Actions network range
- GKE CI setup allows the GitHub Actions runner network range
- CI cluster creation disables selected GKE and AKS components
- Docs-builder image tag update target and stale-base check
- Expanded verifier test logs
- Verifier test parser updated for newer log formats
- Documentation on WireGuard port reservation with DNS proxy transparent mode
- L3/DNS policy documentation clarifies the required `rules.dns` block
- Documentation builds made compatible with macOS
- Host-network access to the Standalone DNS Proxy API documented
- IPv6 cluster-pool IPAM mask-size troubleshooting documentation
- Unnecessary docs-builder image build removed from documentation workflow
- Docker archive ownership normalized in `make render-docs`
- Documentation minimum requirements and builder dependencies updated
- `update-requirements` target uses the documentation minimum requirements file
- TLS visibility documentation updated with the `SDS` abbreviation

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
