https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 19:04:31 +0000 https://cve.radiocsirt.org/vuln/bit-cilium-2023-41332 <p><strong>Affected:</strong> Bitnami: cilium</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In Cilium clusters where Cilium&#39;s Layer 7 proxy has been disabled, creating workloads with `policy.cilium.io/proxy-visibility` annotations (in Cilium &gt;= v1.13) or `io.cilium.proxy-visibility` annotations (in Cilium &lt;= v1.12) causes the Cilium agent to segfault on the node to which the workload is assigned. Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users unable to upgrade can avoid this denial of service attack by enabling the Layer 7 proxy.</p> <p><strong>Affected:</strong> Bitnami: cilium</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In Cilium clusters where Cilium&#39;s Layer 7 proxy has been disabled, creating workloads with `policy.cilium.io/proxy-visibility` annotations (in Cilium &gt;= v1.13) or `io.cilium.proxy-visibility` annotations (in Cilium &lt;= v1.12) causes the Cilium agent to segfault on the node to which the workload is assigned. Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users unable to upgrade can avoid this denial of service attack by enabling the Layer 7 proxy.</p> https://cve.radiocsirt.org/vuln/bit-cilium-2023-41332 https://cve.radiocsirt.org/vuln/euvd-2026-187327 EUVD-2026-187327 https://cve.radiocsirt.org/vuln/euvd-2026-187327 https://cve.radiocsirt.org/vuln/fkie_cve-2023-41332 <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In Cilium clusters where Cilium&#39;s Layer 7 proxy has been disabled, creating workloads with `policy.cilium.io/proxy-visibility` annotations (in Cilium &gt;= v1.13) or `io.cilium.proxy-visibility` annotations (in Cilium &lt;= v1.12) causes the Cilium agent to segfault on the node to which the workload is assigned. Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users unable to upgrade can avoid this denial of service attack by enabling the Layer 7 proxy.</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In Cilium clusters where Cilium&#39;s Layer 7 proxy has been disabled, creating workloads with `policy.cilium.io/proxy-visibility` annotations (in Cilium &gt;= v1.13) or `io.cilium.proxy-visibility` annotations (in Cilium &lt;= v1.12) causes the Cilium agent to segfault on the node to which the workload is assigned. Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users unable to upgrade can avoid this denial of service attack by enabling the Layer 7 proxy.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-41332 https://cve.radiocsirt.org/vuln/ghsa-24m5-r6hv-ccgp <p><strong>Affected:</strong> Go: github.com/cilium/cilium</p> <p>### Impact</p> <p>In Cilium clusters where Cilium&#39;s Layer 7 proxy has been disabled, creating workloads with</p> <p>- `policy.cilium.io/proxy-visibility` annotations (in Cilium &gt;= v1.13) - `io.cilium.proxy-visibility` annotations (in Cilium &lt;= v1.12)</p> <p>causes the Cilium agent to segfault on the node to which the workload is assigned.</p> <p>Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks.</p> <p>### Patches</p> <p>[Pull request with fix](https://github.com/cilium/cilium/pull/27597)</p> <p>This issue affects:</p> <p>Cilium &lt;= v1.14.1 Cilium &lt;= v1.13.6 Cilium &lt;= v1.12.13</p> <p>This issue has been resolved in:</p> <p>Cilium v1.14.2 Cilium v1.13.7 Cilium v1.12.14</p> <p>### Workarounds</p> <p>Users can avoid this denial of service attack by enabling the Layer 7 proxy.</p> <p>### For more information If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).</p> <p>As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - first,…</p> <p><strong>Affected:</strong> Go: github.com/cilium/cilium</p> <p>### Impact</p> <p>In Cilium clusters where Cilium&#39;s Layer 7 proxy has been disabled, creating workloads with</p> <p>- `policy.cilium.io/proxy-visibility` annotations (in Cilium &gt;= v1.13) - `io.cilium.proxy-visibility` annotations (in Cilium &lt;= v1.12)</p> <p>causes the Cilium agent to segfault on the node to which the workload is assigned.</p> <p>Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks.</p> <p>### Patches</p> <p>[Pull request with fix](https://github.com/cilium/cilium/pull/27597)</p> <p>This issue affects:</p> <p>Cilium &lt;= v1.14.1 Cilium &lt;= v1.13.6 Cilium &lt;= v1.12.13</p> <p>This issue has been resolved in:</p> <p>Cilium v1.14.2 Cilium v1.13.7 Cilium v1.12.14</p> <p>### Workarounds</p> <p>Users can avoid this denial of service attack by enabling the Layer 7 proxy.</p> <p>### For more information If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).</p> <p>As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - first,…</p> https://cve.radiocsirt.org/vuln/ghsa-24m5-r6hv-ccgp https://cve.radiocsirt.org/vuln/gsd-2023-41332 gsd-2023-41332 https://cve.radiocsirt.org/vuln/gsd-2023-41332