Skip to content

fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] - #573

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-github.com-cilium-cilium-vulnerability
Open

fix(deps): update module github.com/cilium/cilium to v1.18.9 [security]#573
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-github.com-cilium-cilium-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Dec 1, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/cilium/cilium v1.18.1v1.18.9 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

CVE-2025-64715 / GHSA-38pp-6gcp-rqvm

More information

Details

Impact

CiliumNetworkPolicys which use egress.toGroups.aws.securityGroupsIds to reference AWS security group IDs that do not exist or are not attached to any network interface may unintentionally allow broader outbound access than intended by the policy authors. In such cases, the toCIDRset section of the derived policy is not generated, which means outbound traffic may be permitted to more destinations than originally intended.

Patches

This issue has been patched in:

  • Cilium v1.18.4
  • Cilium v1.17.10
  • Cilium v1.16.17
This issue affects:
  • Cilium v1.18 between v1.18.0 and v1.18.3 inclusive
  • Cilium v1.17 between v1.17.0 and v1.17.9 inclusive
  • Cilium v1.16.16 and below
Workarounds

There is no workaround to this issue.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @​SeanEmac for reporting this issue and to @​fristonio for the patch.

For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

Severity

  • CVSS Score: 4.0 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled

CVE-2026-26963 / GHSA-5r23-prx4-mqg3

More information

Details

Impact

Host Policies will incorrectly permit traffic from Pods on other nodes when all of the following configurations are enabled:

These options are disabled by default in Cilium.

Patches

This issue was fixed by #​42892.

This issue affects:

  • Cilium v1.18 between v1.18.0 and v1.18.5 inclusive

This issue is fixed in:

  • Cilium v1.18.6
Workarounds

There is currently no officially verified or comprehensive workaround for this issue. The following procedure has been validated strictly within a local 'Kind' environment and has not undergone exhaustive testing across diverse production architectures. Proceed with caution.

To mitigate the identified traffic bypass, ensure all ingress traffic from the cilium_wg0 interface is explicitly routed to cilium_host for policy enforcement. This ensures that host-level security policies are applied to decrypted WireGuard traffic. Execute the following configuration on each CiliumNode:

##### IPv4 Traffic
ip rule add iif cilium_wg0 table 300
ip route add default dev cilium_host table 300

##### IPv6 Traffic
ip -6 rule add iif cilium_wg0 table 300
ip -6 route add default dev cilium_net table 300
Acknowledgements

Special thanks to @​julianwiedmann for reporting the issue and helping with the resolution.

For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and your report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.

Severity

  • CVSS Score: 6.1 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic

CVE-2026-33726 / GHSA-hxv8-4j4r-cqgv

More information

Details

Impact

Ingress Network Policies are not enforced for traffic from pods to L7 Services (Envoy, GAMMA) with a local backend on the same node, when Per-Endpoint Routing is enabled and BPF Host Routing is disabled.

Per-Endpoint Routing is disabled by default, but is automatically enabled in deployments using cloud IPAM, including Cilium ENI on EKS (eni.enabled), AlibabaCloud ENI (alibabacloud.enabled), Azure IPAM (azure.enabled, but not AKS BYOCNI), and some GKE deployments (gke.enabled; managed offerings such as GKE Dataplane V2 may use different defaults). It is typically not enabled in tunneled deployments, and chaining deployments are not affected. In practice, Amazon EKS with Cilium ENI mode is likely the most common affected environment.

Patches

This issue was fixed by #​44693.

This issue affects:

  • Cilium v1.19 between v1.19.0 and v1.19.1 inclusive
  • Cilium v1.18 between v1.18.0 and v1.18.7 inclusive
  • All versions of Cilium prior to v1.17.13

This issue is fixed in:

  • Cilium v1.19.2
  • Cilium v1.18.8
  • Cilium v1.17.14
Workarounds

Disclaimer: There is currently no officially verified or comprehensive workaround for this issue. The only option would be to disable per-endpoint routes, but this will likely cause disruptions to ongoing connections, and potential conflicts if running in cloud providers.

Acknowledgements

The Cilium community has worked together with members of the Northflank and Isovalent teams to prepare these mitigations. Cilium thanks @​sudeephb and @​Champ-Goblem for reporting the issue and to @​smagnani96 and @​julianwiedmann for helping with the resolution.

For more information

Anyone who believes a vulnerability affecting Cilium has been found is strongly encouraged to report it to the security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and any such report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.

Severity

  • CVSS Score: 5.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Cillium exposes sensitive information included in the cilium-bugtool debug archive

CVE-2026-41520 / GHSA-gj49-89wh-h4gj

More information

Details

Impact

The output of cilium-bugtool can contain sensitive data when the tool is run against Cilium deployments with WireGuard encryption enabled.

Users of WireGuard Transparent Encryption are affected.
The sensitive data is the WireGuard private key (cilium_wg0.key) used for node-to-node encrypted communication

cilium-bugtool is a debugging tool that is typically invoked manually and does not run during the normal operation of a Cilium cluster. It is also invoked when gathering sysdumps using the Cilium CLI's cilium sysdump command.

Patches

This issue affects:

  • Cilium v1.19 between v1.19.0 and v1.19.2 inclusive
  • Cilium v1.18 between v1.18.0 and v1.18.8 inclusive
  • All versions of Cilium prior to v1.17.15

This issue has been patched in:

  • Cilium v1.19.3
  • Cilium v1.18.9
  • Cilium v1.17.15
Workarounds

There is no workaround to this issue.

Users who have previously shared bugtool or sysdump archives from WireGuard-enabled nodes should rotate the WireGuard keys on the affected nodes. This can be done by deleting the key file and restarting the Cilium agent, which will generate a new key pair.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Cillium extends special thanks to @​kodareef5 for reporting the issue and @​tklauser for their work on triaging and remediating this issue.

For more information

If there are any questions or comments about this advisory, please reach out on Slack.

Cilium strongly encourages the reporting of suspected vulnerabilities to the security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and the report will be treated as top priority.

Severity

  • CVSS Score: 7.9 / 10 (High)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access

CVE-2026-49445 / GHSA-3fcv-jvfp-m4q9

More information

Details

Impact

When Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as:

  • Exposing TLS secrets
  • Disrupting traffic in the cluster
  • Terminating the Envoy process

This issue affects both the embedded and standalone Envoy deployment models.

Patches

This issue affects:

  • Cilium v1.19 between v1.19.0 and v1.19.1 inclusive
  • Cilium v1.18 between v1.18.0 and v1.18.7 inclusive
  • All versions of Cilium prior to v1.17.14

This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in:

  • Cilium v1.19.2
  • Cilium v1.18.8
  • Cilium v1.17.14
Workarounds

There is no known workaround to this issue.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to moemen for reporting the issue and 0xch4z for their work on triaging and remediating this issue.

For more information

If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/).

If anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.

Severity

  • CVSS Score: 9.2 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

cilium/cilium (github.com/cilium/cilium)

v1.18.9: 1.18.9

Compare Source

Summary of Changes

Minor Changes:

Bugfixes:

CI Changes:

Misc Changes:

Other Changes:

Docker Manifests

cilium

quay.io/cilium/cilium:v1.18.9@sha256:c9140c2ebcc636ba346a4152fb28d616a4a51586c22c72dcd6f273bed41053c0

clustermesh-apiserver

quay.io/cilium/clustermesh-apiserver:v1.18.9@sha256:140bbb0433dbdb12e3ab0aaca0cb6fd1a8430812816ccff54c0d7f0adb713175

docker-plugin

quay.io/cilium/docker-plugin:v1.18.9@sha256:da9e6d08f8c11624619692af7ae022b2a7e8e1136d9164910bc6776acdc60079

hubble-relay

quay.io/cilium/hubble-relay:v1.18.9@sha256:031288422f2b0bfff3372fba9812d2867dd9262a6f12c6e6282cfebe54e5efe1

operator-alibabacloud

quay.io/cilium/operator-alibabacloud:v1.18.9@sha256:2116cd9ec94484a1bb7f5cb9703fb6d7c4e63b11431cf145280abda218f3e8b9

operator-aws

quay.io/cilium/operator-aws:v1.18.9@sha256:48d78a4d22fc055a2223019941fc30a51f8a980691e55225bfd6b9cffb164a45

operator-azure

quay.io/cilium/operator-azure:v1.18.9@sha256:4523175c9452c2eab7fa537faa85654120e29b740843f72d55b43c5cbc774f71

operator-generic

quay.io/cilium/operator-generic:v1.18.9@sha256:9094fe19965c558bc9361aa4f0d19fcc48f7377f835dc70f138bf4dc1db48ca4

operator

quay.io/cilium/operator:v1.18.9@sha256:da7b86562f4db18d61e6d34bb1f998d826f993af9d2047bf3e0b7346f658d65c

v1.18.8: 1.18.8

Compare Source

Known issues

  • Users who deploy Cilium on GKE should skip this version or upgrade to 1.19.2 due to a known regression.

Summary of Changes

Minor Changes:

  • Allow to attach Cilium's XDP program on network interfaces that have jumbo MTU configured and support xdp.frags program type. (Backport PR #​44499, Upstream PR #​41967, @​viktor-kurchenko)

Bugfixes:

CI Changes:

Misc Changes:

Other Changes:

Docker Manifests

cilium

quay.io/cilium/cilium:v1.18.8@sha256:070a63cc414869cf6c53202cb50929a87adb7d5b25de0f2f40ab39eb6434b706

clustermesh-apiserver

quay.io/cilium/clustermesh-apiserver:v1.18.8@sha256:5cb08daad7397f52ce5c36fcbfe83c56494f340d9b8f10f8bc7a3f2a812c33d5

docker-plugin

quay.io/cilium/docker-plugin:v1.18.8@sha256:8e1c89bc4ef3bbc55a10edc96a9f2915af45181e46ff189c00f3d8fb7825a0b7

hubble-relay

quay.io/cilium/hubble-relay:v1.18.8@sha256:dcf324aa35ab59c8fe6d002e3df6a63fff18280da464d09e4a97d58c085bb015

operator-alibabacloud

quay.io/cilium/operator-alibabacloud:v1.18.8@sha256:36c1702c8afd0b0221e3d88ca08537100caef509de6a6bb7244d5fa4643a7252

operator-aws

quay.io/cilium/operator-aws:v1.18.8@sha256:7ab154b269eae378456d63cc9085d96c4f472e11a1496ca4c62af68ff4b31da3

operator-azure

quay.io/cilium/operator-azure:v1.18.8@sha256:a4027d349e817bda9168af1e27231be491a3026c748128a79026e366321f6332

operator-generic

quay.io/cilium/operator-generic:v1.18.8@sha256:f9d1715932751b1454d0f59b492497cb1636dea6335beab0f9026fa8b5a6f62f

operator

quay.io/cilium/operator:v1.18.8@sha256:cc3f7bdf9e443b807d3cb9b0bd30eddac5591c3f4b1e6fa053bfaa8697a7ee58

v1.18.7: 1.18.7

Compare Source

Summary of Changes

Minor Changes:

  • Exclude topology.kubernetes.io labels from security labels by default (Backport PR #​43777, Upstream PR #​43725, @​moscicky)
  • hubble-relay: Add hubble.relay.logOptions.format and hubble.relay.logOptions.level Helm values to configure log format (text, text-ts, json, json-ts) and level (debug, info, warn, error) (Backport PR #​44004, Upstream PR #​43644, @​puwun)

Bugfixes:

  • Add permissions to the cilium-operator so that it can create EndpointSlices when the admission plugin OwnerReferencesPermissionEnforcement is activated (Backport PR #​44034, Upstream PR #​43912, @​fgiloux)
  • bpf: Correct refinement of inner packet L4 checksum detection (Backport PR #​43923, Upstream PR #​43868, @​br4243)
  • bpf: Fix marker to skip nodeport when punting to proxy (Backport PR #​43886, Upstream PR #​43069, @​borkmann)
  • clustermesh: correctly phase out not ready/not service endpoints from global services (Backport PR #​44056, Upstream PR #​43807, @​MrFreezeex)
  • Fix a bug with local redirect service entries being created when backend pods weren't ready. (Backport PR #​43756, Upstream PR #​43095, @​aditighag)
  • Fix ICMP error packet handling by adding the missing checksum recalculation performed during RevNAT for SNATed load-balanced traffic. (Backport PR #​43861, Upstream PR #​43196, @​yushoyamaguchi)
  • Grant permissions to the cilium-operator so that it can reconcile ingresses when the when the admission plugin OwnerReferencesPermissionEnforcement is activated (Backport PR #​44034, Upstream PR #​43949, @​giorio94)
  • helm: Fixed RBAC errors with operator.enabled=false by aligning cilium-tlsinterception-secrets Role/RoleBinding conditionals (Backport PR #​44281, Upstream PR #​44159, @​puwun)
  • loadbalancer: Fix GetInstancesOfService to avoid removing an endpoint from Service A causes all requests to Service B to fail if the name of Service A is the prefix of Service B (Backport PR #​43777, Upstream PR #​43620, @​imroc)
  • Reduces rtnl_mutex contention on SR-IOV nodes by not requesting VF information in netlink RTM_GETLINK operations (Backport PR #​44281, Upstream PR #​43517, @​pasteley)

CI Changes:

Misc Changes:

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Dec 1, 2025

Copy link
Copy Markdown
Contributor Author

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 1 additional dependency was updated

Details:

Package Change
github.com/go-viper/mapstructure/v2 v2.3.0 -> v2.4.0

@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 07a4245 to 79c3a65 Compare December 6, 2025 03:46
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 79c3a65 to d845265 Compare January 1, 2026 20:51
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 4ca315a to 62de554 Compare January 30, 2026 01:35
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.4 [security] fix(deps): update module github.com/cilium/cilium to v1.18.4 [security] - autoclosed Feb 7, 2026
@renovate renovate Bot closed this Feb 7, 2026
@renovate
renovate Bot deleted the renovate/go-github.com-cilium-cilium-vulnerability branch February 7, 2026 02:10
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.4 [security] - autoclosed fix(deps): update module github.com/cilium/cilium to v1.18.4 [security] Feb 7, 2026
@renovate renovate Bot reopened this Feb 7, 2026
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 62de554 to 2c0602f Compare February 7, 2026 05:29
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 2c0602f to 9e82cd6 Compare February 20, 2026 17:03
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.4 [security] fix(deps): update module github.com/cilium/cilium to v1.18.6 [security] Feb 20, 2026
@renovate

renovate Bot commented Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 8 additional dependencies were updated

Details:

Package Change
cel.dev/expr v0.24.0 -> v0.25.1
github.com/cilium/ebpf v0.19.0 -> v0.20.1-0.20260218191617-ee67e7f43dd9
github.com/cilium/statedb v0.4.5 -> v0.4.6
github.com/go-jose/go-jose/v4 v4.1.3 -> v4.1.4
github.com/vishvananda/netlink v1.3.1 -> v1.3.2-0.20250926155043-cd3cb2e12c97
google.golang.org/grpc v1.78.0 -> v1.79.3
k8s.io/kubectl v0.33.3 -> v0.33.10
k8s.io/utils v0.0.0-20260108192941-914a6e750570 -> v0.0.0-20260319190234-28399d86e0b5

@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 9e82cd6 to 33b2d77 Compare February 24, 2026 12:42
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from cbfc98c to 50a51c8 Compare March 26, 2026 17:13
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.6 [security] fix(deps): update module github.com/cilium/cilium to v1.18.8 [security] Mar 26, 2026
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 4 times, most recently from 96c09e4 to 2706cef Compare April 3, 2026 01:26
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 2706cef to 11d1637 Compare April 16, 2026 16:15
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.8 [security] fix(deps): update module github.com/cilium/cilium to v1.18.8 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.8 [security] - autoclosed fix(deps): update module github.com/cilium/cilium to v1.18.8 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 11d1637 to 127bb7d Compare April 27, 2026 22:03
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 127bb7d to 01e78a9 Compare May 6, 2026 12:59
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.8 [security] fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] May 6, 2026
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] - autoclosed May 19, 2026
@renovate renovate Bot closed this May 19, 2026
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] - autoclosed fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] May 19, 2026
@renovate renovate Bot reopened this May 19, 2026
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 01e78a9 to 1470720 Compare May 19, 2026 10:36
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 1470720 to 743dfb0 Compare June 12, 2026 18:14
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] - autoclosed Jun 18, 2026
@renovate renovate Bot closed this Jun 18, 2026
@renovate renovate Bot changed the title fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] - autoclosed fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] Jun 18, 2026
@renovate renovate Bot reopened this Jun 18, 2026
@renovate
renovate Bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 743dfb0 to 8f73a32 Compare June 18, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants