<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T19:08:53.895113+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-cilium-2023-27593</id>
    <title>BIT-cilium-2023-27593 — cilium-agent container can access the host via `hostPath` mount</title>
    <updated>2026-10-10T19:08:53.898415+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: cilium</p>
<p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, an attacker with access to a Cilium agent pod can write to `/opt/cni/bin` due to a `hostPath` mount of that directory in the agent pod. By replacing the CNI binary with their own malicious binary and waiting for the creation of a new pod on the node, the attacker can gain access to the underlying node.</p>
<p>The issue has been fixed and the fix is available on versions 1.11.15, 1.12.8, and 1.13.1. Some workarounds are available. Kubernetes RBAC should be used to deny users and service accounts `exec` access to Cilium agent pods. In cases where a user requires `exec` access to Cilium agent pods, but should not have access to the underlying node, no workaround is possible.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-cilium-2023-27593"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-218846</id>
    <title>EUVD-2026-218846</title>
    <updated>2026-10-10T19:08:53.898471+00:00</updated>
    <content>EUVD-2026-218846</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-218846"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-27593</id>
    <title>fkie_cve-2023-27593</title>
    <updated>2026-10-10T19:08:53.898489+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, an attacker with access to a Cilium agent pod can write to `/opt/cni/bin` due to a `hostPath` mount of that directory in the agent pod. By replacing the CNI binary with their own malicious binary and waiting for the creation of a new pod on the node, the attacker can gain access to the underlying node.</p>
<p>The issue has been fixed and the fix is available on versions 1.11.15, 1.12.8, and 1.13.1. Some workarounds are available. Kubernetes RBAC should be used to deny users and service accounts `exec` access to Cilium agent pods. In cases where a user requires `exec` access to Cilium agent pods, but should not have access to the underlying node, no workaround is possible.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-27593"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4hc4-pgfx-3mrx</id>
    <title>GHSA-4hc4-pgfx-3mrx — cilium-agent container can access the host via `hostPath` mount</title>
    <updated>2026-10-10T19:08:53.898516+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/cilium/cilium</p>
<p>### Impact</p>
<p>An attacker with access to a Cilium agent pod can write to `/opt/cni/bin` due to a `hostPath` mount of that directory in the agent pod. By replacing the CNI binary with their own malicious binary and waiting for the creation of a new pod on the node, the attacker can gain access to the underlying node.</p>
<p>### Patches</p>
<p>The issue has been fixed and is available on versions &gt;=1.11.15, &gt;=1.12.8, &gt;=1.13.1.</p>
<p>### Workarounds</p>
<p>[Kubernetes RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) should be used to deny users and service accounts `exec` access to Cilium agent pods.</p>
<p>In cases where a user requires `exec` access to Cilium agent pods, but should not have access to the underlying node, no workaround is possible.</p>
<p>### References</p>
<p>* [PR containing resolution](https://github.com/cilium/cilium/pull/24075)</p>
<p>### Acknowledgements</p>
<p>The Cilium community has worked together with members of Isovalent and Form3 to prepare these mitigations. Special thanks to Anastasios Koutlis, Daniel Teixeira, and Magdalena Oczadly for their cooperation.</p>
<p>### For more information</p>
<p>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 - first, before disclosing them in any public forums. This is a private maili…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4hc4-pgfx-3mrx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-27593</id>
    <title>gsd-2023-27593</title>
    <updated>2026-10-10T19:08:53.898564+00:00</updated>
    <content>gsd-2023-27593</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-27593"/>
  </entry>
</feed>
