Cilium v1.18.16, published on October 23, 2026, is a security patch release that upgrades Go to 1.26.10 to remove trust in compromised eMudhra intermediate CA certificates. It also corrects Envoy service namespace handling, a change worth checking on Kubernetes clusters that carry ingestion and processing traffic. This is a stable release.
The full release notes and image manifests are on the GitHub release page.
Go 1.26.10 changes certificate trust ¶
The project issued this patch outside its normal release schedule to address CVE-2026-111943. The notes identify Go 1.26.10 as the fix and link to the Go certificate trust issue. The stated result is specific: the compromised eMudhra intermediate CA certificates are no longer trusted.
That trust change is the main reason to evaluate this release. For operators, the expected consequence is rejection of certificates that depend on the removed trust. If a connection relies on one of those intermediates, certificate validation deserves attention during rollout. Successful pod startup alone would not exercise that connection.
The release also updates all dependencies to their latest patch versions, according to the summary. Treat that as part of the patch scope when reviewing the deployed artifacts. The notes do not enumerate every dependency version, so the summary cannot establish the effect of each individual update. The concrete security change documented here is the Go certificate trust correction.
Envoy service references regain namespace boundaries ¶
CiliumEnvoyConfig now redirects Services only in its own namespace, matching the documented behavior. The useful review target is any configuration that previously depended on redirecting a Service in another namespace. That dependency needs attention because the corrected scope excludes it.
For example, consider a CiliumEnvoyConfig in an ingestion namespace and a Service in a separate processing namespace. Under the behavior described for v1.18.16, that configuration only redirects Services in the ingestion namespace.
The second correction affects CiliumClusterwideEnvoyConfig. Service references that omit a namespace resolve to default again. An omitted namespace therefore has a defined destination. When reviewing shared configuration, check each reference against the namespace of the intended Service, especially where multiple namespaces contain Services with the same name.
For a data platform, these fixes deserve a traffic check through the affected Services. An ingestion endpoint can exist while its expected redirect no longer matches the configuration’s scope. Inspect the namespaced and clusterwide resources separately, then exercise the request path used by the pipeline. The release notes describe a bugfix restoring documented behavior; they provide no separate migration procedure.
Signing verification and release image selection ¶
The signing documentation now clarifies the minimum tool version needed to verify the signing key. That matters when image verification gates deployment. Check the clarified requirement against the verifier used by the promotion job. The changelog does not state the minimum version number. Use the updated signing documentation to check that prerequisite.
The supplied manifests include tag and SHA256 references for the Cilium image, clustermesh-apiserver, hubble-relay, and the operator variants. Use the manifest for the component being deployed when recording the v1.18.16 artifact. A rollout inventory should identify which listed components the cluster actually runs and which image references need updating.
The remaining CI entries concern the project’s build and dependency automation. They are maintenance changes for producing the release, with no operator configuration steps stated in the notes.