fix(deps): update module github.com/cilium/cilium to v1.18.9 [security] - #573
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update module github.com/cilium/cilium to v1.18.9 [security]#573renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
December 6, 2025 03:46
07a4245 to
79c3a65
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
January 1, 2026 20:51
79c3a65 to
d845265
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
2 times, most recently
from
January 30, 2026 01:35
4ca315a to
62de554
Compare
renovate
Bot
deleted the
renovate/go-github.com-cilium-cilium-vulnerability
branch
February 7, 2026 02:10
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
2 times, most recently
from
February 7, 2026 05:29
62de554 to
2c0602f
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
February 20, 2026 17:03
2c0602f to
9e82cd6
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
February 24, 2026 12:42
9e82cd6 to
33b2d77
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
2 times, most recently
from
March 26, 2026 17:13
cbfc98c to
50a51c8
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
4 times, most recently
from
April 3, 2026 01:26
96c09e4 to
2706cef
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
April 16, 2026 16:15
2706cef to
11d1637
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
2 times, most recently
from
April 27, 2026 22:03
11d1637 to
127bb7d
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
May 6, 2026 12:59
127bb7d to
01e78a9
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
2 times, most recently
from
May 19, 2026 10:36
01e78a9 to
1470720
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
from
June 12, 2026 18:14
1470720 to
743dfb0
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-cilium-cilium-vulnerability
branch
2 times, most recently
from
June 18, 2026 18:48
743dfb0 to
8f73a32
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.18.1→v1.18.9Warning
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 useegress.toGroups.aws.securityGroupsIdsto 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:
This issue affects:
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:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
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:
This issue is fixed in:
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_wg0interface is explicitly routed tocilium_hostfor policy enforcement. This ensures that host-level security policies are applied to decrypted WireGuard traffic. Execute the following configuration on each CiliumNode: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:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NReferences
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:
This issue is fixed in:
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:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NReferences
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-bugtoolcan 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 communicationcilium-bugtoolis 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'scilium sysdumpcommand.Patches
This issue affects:
This issue has been patched in:
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:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NReferences
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:
This issue affects both the embedded and standalone Envoy deployment models.
Patches
This issue affects:
This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in:
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:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:HReferences
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.9Compare Source
Summary of Changes
Minor Changes:
Bugfixes:
hubble observecaused by log coloring feature, even when coloring was disabled (Backport PR #44827, Upstream PR #44119, @tporeba)CI Changes:
Misc Changes:
tc_classidon all ingress code paths (Backport PR #45213, Upstream PR #42105, @pchaigno)1487d0a(v1.18) (#45040, @cilium-renovate[bot])a95d3d1(v1.18) (#45316, @cilium-renovate[bot])186072b(v1.18) (#44935, @cilium-renovate[bot])84e77de(v1.18) (#45306, @cilium-renovate[bot])28399d8(v1.18) (#44936, @cilium-renovate[bot])4b9911b(v1.18) (#45170, @cilium-renovate[bot])Other Changes:
tc_classidon all ingress code paths (#45341, @pchaigno)Docker Manifests
cilium
quay.io/cilium/cilium:v1.18.9@sha256:c9140c2ebcc636ba346a4152fb28d616a4a51586c22c72dcd6f273bed41053c0clustermesh-apiserver
quay.io/cilium/clustermesh-apiserver:v1.18.9@sha256:140bbb0433dbdb12e3ab0aaca0cb6fd1a8430812816ccff54c0d7f0adb713175docker-plugin
quay.io/cilium/docker-plugin:v1.18.9@sha256:da9e6d08f8c11624619692af7ae022b2a7e8e1136d9164910bc6776acdc60079hubble-relay
quay.io/cilium/hubble-relay:v1.18.9@sha256:031288422f2b0bfff3372fba9812d2867dd9262a6f12c6e6282cfebe54e5efe1operator-alibabacloud
quay.io/cilium/operator-alibabacloud:v1.18.9@sha256:2116cd9ec94484a1bb7f5cb9703fb6d7c4e63b11431cf145280abda218f3e8b9operator-aws
quay.io/cilium/operator-aws:v1.18.9@sha256:48d78a4d22fc055a2223019941fc30a51f8a980691e55225bfd6b9cffb164a45operator-azure
quay.io/cilium/operator-azure:v1.18.9@sha256:4523175c9452c2eab7fa537faa85654120e29b740843f72d55b43c5cbc774f71operator-generic
quay.io/cilium/operator-generic:v1.18.9@sha256:9094fe19965c558bc9361aa4f0d19fcc48f7377f835dc70f138bf4dc1db48ca4operator
quay.io/cilium/operator:v1.18.9@sha256:da7b86562f4db18d61e6d34bb1f998d826f993af9d2047bf3e0b7346f658d65cv1.18.8: 1.18.8Compare Source
Known issues
Summary of Changes
Minor Changes:
Bugfixes:
ip get -l reserved:host(Backport PR #44519, Upstream PR #44443, @aanm)CI Changes:
Misc Changes:
d1e2e92(v1.18) (#44476, @cilium-renovate[bot])e3f9456(v1.18) (#44797, @cilium-renovate[bot])f512d81(v1.18) (#44575, @cilium-renovate[bot])0f775a3(v1.18) (#44576, @cilium-renovate[bot])15301c2(v1.18) (#44675, @cilium-renovate[bot])Other Changes:
Docker Manifests
cilium
quay.io/cilium/cilium:v1.18.8@sha256:070a63cc414869cf6c53202cb50929a87adb7d5b25de0f2f40ab39eb6434b706clustermesh-apiserver
quay.io/cilium/clustermesh-apiserver:v1.18.8@sha256:5cb08daad7397f52ce5c36fcbfe83c56494f340d9b8f10f8bc7a3f2a812c33d5docker-plugin
quay.io/cilium/docker-plugin:v1.18.8@sha256:8e1c89bc4ef3bbc55a10edc96a9f2915af45181e46ff189c00f3d8fb7825a0b7hubble-relay
quay.io/cilium/hubble-relay:v1.18.8@sha256:dcf324aa35ab59c8fe6d002e3df6a63fff18280da464d09e4a97d58c085bb015operator-alibabacloud
quay.io/cilium/operator-alibabacloud:v1.18.8@sha256:36c1702c8afd0b0221e3d88ca08537100caef509de6a6bb7244d5fa4643a7252operator-aws
quay.io/cilium/operator-aws:v1.18.8@sha256:7ab154b269eae378456d63cc9085d96c4f472e11a1496ca4c62af68ff4b31da3operator-azure
quay.io/cilium/operator-azure:v1.18.8@sha256:a4027d349e817bda9168af1e27231be491a3026c748128a79026e366321f6332operator-generic
quay.io/cilium/operator-generic:v1.18.8@sha256:f9d1715932751b1454d0f59b492497cb1636dea6335beab0f9026fa8b5a6f62foperator
quay.io/cilium/operator:v1.18.8@sha256:cc3f7bdf9e443b807d3cb9b0bd30eddac5591c3f4b1e6fa053bfaa8697a7ee58v1.18.7: 1.18.7Compare Source
Summary of Changes
Minor Changes:
hubble.relay.logOptions.formatandhubble.relay.logOptions.levelHelm 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:
operator.enabled=falseby aligning cilium-tlsinterception-secrets Role/RoleBinding conditionals (Backport PR #44281, Upstream PR #44159, @puwun)CI Changes:
Misc Changes:
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.