# Cilium v1.16.18

2025-12-18 · [Original release notes](https://github.com/cilium/cilium/releases/tag/v1.16.18) · [Full summary](https://ratatosk.io/en/releases/cilium/v1.16.18)

Security 1 · Breaking changes 1 · Important fixes 8 · Dependency updates 22 · Other changes 27

## Security (1)

### SSH GSSAPI mechanism-count validation added

- Affects: SSH servers parsing GSSAPI authentication requests with `golang.org/x/crypto`
- [CVE-2025-58181](https://www.cve.org/CVERecord?id=CVE-2025-58181)

Previously, an unchecked mechanism count in a GSSAPI authentication request could cause unbounded memory consumption. The parser now rejects counts above 64 or inconsistent with the remaining payload with `invalid mechanism count`.

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

## Breaking changes (1)

### Dockerfile image defaults updated

- Affects: Builds using the affected image Dockerfiles, including those relying on the `CILIUM_RUNTIME_IMAGE` or `CILIUM_BUILDER_IMAGE` defaults (Inferred)

The `CILIUM_RUNTIME_IMAGE` and `CILIUM_BUILDER_IMAGE` defaults now point to newer image references.

Evidence: “-ARG CILIUM_RUNTIME_IMAGE=quay.io/cilium/cilium-runtime:affff2c98da6fc08fb342e2ec2f7d72bcec6faf3@sha256:b1bfdc9e4dacd46fce72c3a351a88ddbc6fd654da06bb248469d054ad0780613 +ARG CILIUM_RUNTIME_IMAGE=quay.io/cilium/cilium-runtime:e0df6af4efcd628e32c971bf39dd54de305c8cba@sha256:0444e3fb784aaf07ad938080925576bfce7ee8ecccd086a278ba724651c296d1” https://github.com/cilium/cilium/pull/43239

> * [v1.16] .github/workflows: make adjustments for new GitHub workflow behavior (cilium/cilium#43239, @aanm)

## Important fixes (8)

### IPsec XFRM rule direction logging fixed

- Affects: IPsec setups that process and log XFRM rules

When IPsec processed and logged XFRM rules, the logs could label them Ingress even when that was incorrect. The logged direction is now determined by comparing the masked XFRM mark with the decrypt and encrypt marks, reporting Ingress or Egress respectively.

> * Fix a bug that would cause IPsec logs to incorrectly report the XFRM rules being processed as "Ingress" rules. (Backport PR cilium/cilium#42826, Upstream PR cilium/cilium#42640, @sjohnsonpal)

### etcd/clustermesh troubleshoot certificate validation fixed

- Affects: etcd/clustermesh troubleshoot certificate validation (Inferred)

Previously, certificate checks did not specify a key usage, and warnings omitted the verification error. They now verify for `ClientAuth` and include the error in the warning when verification fails.

> * Minor improvements around certificate validation in etcd/clustermesh troubleshoot commands (Backport PR cilium/cilium#42951, Upstream PR cilium/cilium#42782, @giorio94)

### AWS EC2 ENI attachment fixed for multi-network-card instances

- Affects: AWS EC2 multi-network-card instances using EFA

When AWS validated available device indexes on these instances, omitting the network card index could interfere with ENI attachment. The attachment call now explicitly sets `NetworkCardIndex` to 0.

> * AWS EC2: Fix ENI attachment on multi-network card instances with high-performance networking (EFA) setups (Backport PR cilium/cilium#42746, Upstream PR cilium/cilium#42512, @41ks)

### `CiliumEnvoyConfig` proxy ports restored after agent restarts

- Affects: setups with proxy ports configured through `CiliumEnvoyConfig`

> * CiliumEnvoyConfig proxy ports are now restored on agent restarts. (Backport PR cilium/cilium#43119, Upstream PR cilium/cilium#43108, @jrajahalme)

### Cilium agent XFRM-state startup failure fixed

- Affects: Setups with IPsec enabled

When the affected XFRM-state handling case occurred, the agent could fail to add XFRM states, preventing proper startup.

> * Fix bug that could cause the agent to fail to add XFRM states when IPsec is enabled, thus preventing a proper startup. (Backport PR cilium/cilium#42951, Upstream PR cilium/cilium#42666, @pchaigno)

### Selector-policy endpoint regeneration deadlock fixed

- Affects: setups where selector-policy replacement coincides with endpoint deletion

When selector-policy replacement coincided with endpoint deletion, the endpoint and selector-policy locks could deadlock. Selector-policy-triggered endpoint regeneration now runs in a goroutine, allowing the selector-policy lock to be released and avoiding the deadlock.

> * policy: Fix Endpoint Selector Policy Deadlock (Backport PR cilium/cilium#43082, Upstream PR cilium/cilium#38139, @nathanjsweet)

### Simultaneous updates for endpoints sharing an identity fixed

- Affects: workloads with endpoints that share an identity

Previously, two endpoints sharing an identity could be prevented from updating at the same time when both were being updated simultaneously.

> * policy: Fix rare bug that prevented two endpoints that shared the same identity from being simultaneously updated. (Backport PR cilium/cilium#43082, Upstream PR cilium/cilium#37910, @nathanjsweet)

### Endpoint regeneration for selector-policy races

- Affects: endpoints sharing an identity and processing policy revisions concurrently

An endpoint could remain stuck with a detached selector policy if another endpoint replaced it before the first ran `DistillPolicy`.

> * policy: Fix rare Endpoint Selector Policy Deadlock causing policies to not be updated with new identities (Backport PR cilium/cilium#43082, Upstream PR cilium/cilium#42306, @odinuge)

## Dependency updates (22)

22 more, none mentioning security

- `* chore(deps): update all-dependencies (v1.16) (cilium/cilium#42809, @cilium-renovate[bot])`
- `* chore(deps): update all-dependencies (v1.16) (cilium/cilium#43041, @cilium-renovate[bot])`
- `* chore(deps): update dependency cilium/cilium-cli to v0.18.9 (v1.16) (cilium/cilium#43191, @cilium-renovate[bot])`
- `* chore(deps): update dependency cilium/little-vm-helper to v0.0.28 (v1.16) (cilium/cilium#42773, @cilium-renovate[bot])`
- `* chore(deps): update dependency protocolbuffers/protobuf to v33.1 (v1.16) (cilium/cilium#42812, @cilium-renovate[bot])`
- `* chore(deps): update dependency protocolbuffers/protobuf to v33.2 (v1.16) (cilium/cilium#43194, @cilium-renovate[bot])`
- `* chore(deps): update dependency protocolbuffers/protobuf-go to v1.36.11 (v1.16) (cilium/cilium#43329, @cilium-renovate[bot])`
- `* chore(deps): update docker.io/library/busybox:1.36.1 docker digest to 6b21990 (v1.16) (cilium/cilium#43326, @cilium-renovate[bot])`
- `* chore(deps): update docker.io/library/golang:1.24.10 docker digest to 7b13449 (v1.16) (cilium/cilium#42939, @cilium-renovate[bot])`
- `* chore(deps): update docker.io/library/golang:1.24.10 docker digest to 83d7392 (v1.16) (cilium/cilium#42810, @cilium-renovate[bot])`
- `* chore(deps): update docker.io/library/golang:1.24.11 docker digest to e3fb71a (v1.16) (cilium/cilium#43327, @cilium-renovate[bot])`
- `* chore(deps): update gcr.io/distroless/static:nonroot docker digest to 2b7c93f (v1.16) (cilium/cilium#43138, @cilium-renovate[bot])`
- `* chore(deps): update go to v1.24.11 (v1.16) (cilium/cilium#43192, @cilium-renovate[bot])`
- `* chore(deps): update quay.io/cilium/certgen docker tag to v0.3.1 (v1.16) (cilium/cilium#43054, @cilium-renovate[bot])`
- `* chore(deps): update quay.io/cilium/cilium-envoy docker tag to v1.34.10-1763384313-86bb34d9627caf54d09233ad653eaf621751d301 (v1.16) (cilium/cilium#42940, @cilium-renovate[bot])`
- `* chore(deps): update stable lvh-images (v1.16) (patch) (cilium/cilium#42811, @cilium-renovate[bot])`
- `* chore(deps): update stable lvh-images (v1.16) (patch) (cilium/cilium#42941, @cilium-renovate[bot])`
- `* chore(deps): update stable lvh-images (v1.16) (patch) (cilium/cilium#43039, @cilium-renovate[bot])`
- `* chore(deps): update stable lvh-images (v1.16) (patch) (cilium/cilium#43193, @cilium-renovate[bot])`
- `* chore(deps): update stable lvh-images (v1.16) (patch) (cilium/cilium#43330, @cilium-renovate[bot])`
- `* [v1.16] proxy: Bump envoy version to v1.34.11 (cilium/cilium#43145, @sayboras)`
- `* [v1.16] proxy: Bump envoy version to v1.34.12 (cilium/cilium#43262, @sayboras)`

## Other changes (27)

- Endpoint ID 1 included in DNS proxy transparent mode
- Worker disk cleanup no longer restricted to `ubuntu-latest` runners
- Egress-gateway BPF test uses `ENABLE_MASQUERADE_IPV4`
- IPSec privileged tests split into parallel and non-parallel runs
- `build-images-hotfixes.yaml` developer hot-fix image build and publish workflow removed
- Makefile non-parallel test package list set to `./pkg/datapath/linux/...`
- Connection-disruption action defaults and test selection
- IPsec end-to-end workflow no longer excludes `no-ipsec-xfrm-error`
- Runner disk cleanup added to the ClusterMesh upgrade workflow
- Conformance clustermesh workflow waits for cert-manager CRDs to be established
- Documentation Makefile target uses BusyBox `awk` and `sed`
- Linux node tests moved to the non-parallel test group
- Auto-approve workflow limits reviewer removal
- Repository workflows reorganized by branch and trigger
- Image-build workflow uses a dynamic `CILIUM_RUNTIME` image
- Development container and test manifest updated to use the `cilium-builder` image
- GitHub Actions `actions/cache` updated to v5.0.1
- GitHub Actions dependencies updated in the v1.16 workflow
- GitHub Actions dependencies updated in the v1.16 workflow
- GitHub Actions dependencies updated in the v1.16 workflow
- GitHub Actions dependencies updated in the v1.16 workflow
- GitHub Actions dependencies updated in the v1.16 workflow
- Documentation of connection-tracking limitations across VIPs and NodePorts
- Host firewall recovery guidance for blocked node access
- The `lint-build-commits` workflow now defaults to `ubuntu-24.04` and installs `libtinfo6`
- CI EKS nodegroup `volumeSize` increased to 25 GB
- Install image digests updated for `v1.16.17`

---

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