<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 19:30:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-323053</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323053</link>
      <description>EUVD-2026-323053</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323053</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44543</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44543</link>
      <description>&lt;p&gt;Local Path Provisioner provides a way for the Kubernetes users to utilize the local storage in each node. Prior to 0.0.36, a malicious user with permission to edit the local-path-config ConfigMap in the local-path-storage namespace can manipulate the helperPod.yaml template used by rancher/local-path-provisioner. The helperPod.yaml template is loaded by the provisioner and used to create HelperPods during PVC provisioning and cleanup operations. However, the template is not sufficiently validated before use. Security-sensitive fields such as securityContext.privileged, hostPath volumes, and Linux capabilities can be injected into the template. When a PVC operation triggers HelperPod creation, the provisioner creates the HelperPod using the attacker-controlled template. This can result in a privileged pod running on the target node with the host root filesystem mounted. This may allow the attacker to access sensitive host files, read ServiceAccount tokens from other pods on the same node, access other tenants&amp;#39; local-path volume data, or modify files on the host node. This vulnerability is fixed in 0.0.36.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Local Path Provisioner provides a way for the Kubernetes users to utilize the local storage in each node. Prior to 0.0.36, a malicious user with permission to edit the local-path-config ConfigMap in the local-path-storage namespace can manipulate the helperPod.yaml template used by rancher/local-path-provisioner. The helperPod.yaml template is loaded by the provisioner and used to create HelperPods during PVC provisioning and cleanup operations. However, the template is not sufficiently validated before use. Security-sensitive fields such as securityContext.privileged, hostPath volumes, and Linux capabilities can be injected into the template. When a PVC operation triggers HelperPod creation, the provisioner creates the HelperPod using the attacker-controlled template. This can result in a privileged pod running on the target node with the host root filesystem mounted. This may allow the attacker to access sensitive host files, read ServiceAccount tokens from other pods on the same node, access other tenants&amp;#39; local-path volume data, or modify files on the host node. This vulnerability is fixed in 0.0.36.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44543</guid>
    </item>
    <item>
      <title>GHSA-7fxv-8wr2-mfc4 — Local Path Provisioner Vulnerable to HelperPod Template Injection</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7fxv-8wr2-mfc4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/local-path-provisioner&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A malicious user with permission to edit the `local-path-config` ConfigMap in the `local-path-storage` namespace can manipulate the `helperPod.yaml` template used by `rancher/local-path-provisioner`.&lt;/p&gt;
&lt;p&gt;The `helperPod.yaml` template is loaded by the provisioner and used to create HelperPods during PVC provisioning and cleanup operations. However, the template is not sufficiently validated before use. Security-sensitive fields such as `securityContext.privileged`, `hostPath` volumes, and Linux capabilities can be injected into the template.&lt;/p&gt;
&lt;p&gt;Example malicious HelperPod template:&lt;/p&gt;
&lt;p&gt;~~~yaml
apiVersion: v1
kind: Pod
metadata:
  name: helper-pod
spec:
  containers:
  - name: helper-pod
    image: docker.io/kindest/local-path-helper:v20230510-486859a6
    imagePullPolicy: IfNotPresent
    securityContext:
      privileged: true
    volumeMounts:
    - name: host-root
      mountPath: /host
  volumes:
  - name: host-root
    hostPath:
      path: /
      type: Directory
~~~&lt;/p&gt;
&lt;p&gt;When a PVC operation triggers HelperPod creation, the provisioner creates the HelperPod using the attacker-controlled template. This can result in a privileged pod running on the target node with the host root filesystem mounted.&lt;/p&gt;
&lt;p&gt;This may allow the attacker to access sensitive host files, read ServiceAccount tokens from other pods on the same node, access other tenants&amp;#39; local-path volume data, or modify files on the host node.&lt;/p&gt;
&lt;p&gt;Expected Behavior:&lt;/p&gt;
&lt;p&gt;- The HelperPod template should not allow privileged c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/local-path-provisioner&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A malicious user with permission to edit the `local-path-config` ConfigMap in the `local-path-storage` namespace can manipulate the `helperPod.yaml` template used by `rancher/local-path-provisioner`.&lt;/p&gt;
&lt;p&gt;The `helperPod.yaml` template is loaded by the provisioner and used to create HelperPods during PVC provisioning and cleanup operations. However, the template is not sufficiently validated before use. Security-sensitive fields such as `securityContext.privileged`, `hostPath` volumes, and Linux capabilities can be injected into the template.&lt;/p&gt;
&lt;p&gt;Example malicious HelperPod template:&lt;/p&gt;
&lt;p&gt;~~~yaml
apiVersion: v1
kind: Pod
metadata:
  name: helper-pod
spec:
  containers:
  - name: helper-pod
    image: docker.io/kindest/local-path-helper:v20230510-486859a6
    imagePullPolicy: IfNotPresent
    securityContext:
      privileged: true
    volumeMounts:
    - name: host-root
      mountPath: /host
  volumes:
  - name: host-root
    hostPath:
      path: /
      type: Directory
~~~&lt;/p&gt;
&lt;p&gt;When a PVC operation triggers HelperPod creation, the provisioner creates the HelperPod using the attacker-controlled template. This can result in a privileged pod running on the target node with the host root filesystem mounted.&lt;/p&gt;
&lt;p&gt;This may allow the attacker to access sensitive host files, read ServiceAccount tokens from other pods on the same node, access other tenants&amp;#39; local-path volume data, or modify files on the host node.&lt;/p&gt;
&lt;p&gt;Expected Behavior:&lt;/p&gt;
&lt;p&gt;- The HelperPod template should not allow privileged c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7fxv-8wr2-mfc4</guid>
    </item>
  </channel>
</rss>
