https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 14 Oct 2026 15:03:04 +0000 https://cve.radiocsirt.org/vuln/bit-cilium-2023-39347 <p><strong>Affected:</strong> Bitnami: cilium</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question. This can affect Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic, Cilium clusterwide network policies that use Cilium namespace labels to select the Pod and Kubernetes network policies. Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the `io.kubernetes.pod.namespace` label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question. This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users are advised to upgrade. As a workaround an admission webhook can be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace` and `io.cilium.k8s.policy.*` keys.</p> <p><strong>Affected:</strong> Bitnami: cilium</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question. This can affect Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic, Cilium clusterwide network policies that use Cilium namespace labels to select the Pod and Kubernetes network policies. Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the `io.kubernetes.pod.namespace` label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question. This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users are advised to upgrade. As a workaround an admission webhook can be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace` and `io.cilium.k8s.policy.*` keys.</p> https://cve.radiocsirt.org/vuln/bit-cilium-2023-39347 https://cve.radiocsirt.org/vuln/euvd-2026-187356 EUVD-2026-187356 https://cve.radiocsirt.org/vuln/euvd-2026-187356 https://cve.radiocsirt.org/vuln/fkie_cve-2023-39347 <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question. This can affect Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic, Cilium clusterwide network policies that use Cilium namespace labels to select the Pod and Kubernetes network policies. Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the `io.kubernetes.pod.namespace` label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question. This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users are advised to upgrade. As a workaround an admission webhook can be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace` and `io.cilium.k8s.policy.*` keys.</p> <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question. This can affect Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic, Cilium clusterwide network policies that use Cilium namespace labels to select the Pod and Kubernetes network policies. Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the `io.kubernetes.pod.namespace` label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question. This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users are advised to upgrade. As a workaround an admission webhook can be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace` and `io.cilium.k8s.policy.*` keys.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-39347 https://cve.radiocsirt.org/vuln/ghsa-gj2r-phwg-6rww <p><strong>Affected:</strong> Go: github.com/cilium/cilium</p> <p>### Impact</p> <p>An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies.</p> <p>This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question.</p> <p>This can affect:</p> <p>* Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic * Cilium clusterwide network policies that use Cilium namespace labels to select the Pod * Kubernetes network policies</p> <p>Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the `io.kubernetes.pod.namespace` label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question.</p> <p>This attack requires the attacker to have [Kubernetes API Server access](https://docs.cilium.io/en/latest/security/threat-model/#kubernetes-api-server-attacker), as described in the Cilium Threat Model.</p> <p>### Patches</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>An admission webhook can be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace` and `io.cilium.k8s.policy.*` keys.</p> <p>### Acknowledgements The Cilium community has worked together with members of Palantir and Isovalent to prepare…</p> <p><strong>Affected:</strong> Go: github.com/cilium/cilium</p> <p>### Impact</p> <p>An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies.</p> <p>This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question.</p> <p>This can affect:</p> <p>* Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic * Cilium clusterwide network policies that use Cilium namespace labels to select the Pod * Kubernetes network policies</p> <p>Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the `io.kubernetes.pod.namespace` label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question.</p> <p>This attack requires the attacker to have [Kubernetes API Server access](https://docs.cilium.io/en/latest/security/threat-model/#kubernetes-api-server-attacker), as described in the Cilium Threat Model.</p> <p>### Patches</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>An admission webhook can be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace` and `io.cilium.k8s.policy.*` keys.</p> <p>### Acknowledgements The Cilium community has worked together with members of Palantir and Isovalent to prepare…</p> https://cve.radiocsirt.org/vuln/ghsa-gj2r-phwg-6rww https://cve.radiocsirt.org/vuln/gsd-2023-39347 gsd-2023-39347 https://cve.radiocsirt.org/vuln/gsd-2023-39347