Attack Chain

1. Attacker gains access to the Kubernetes cluster.
2. Attacker obtains permission to edit the local-path-config ConfigMap within the local-path-storage namespace.
3. Attacker modifies the helperPod.yaml template within the local-path-config ConfigMap to inject malicious configurations, such as setting securityContext.privileged to true or adding a hostPath volume mount.
4. Attacker triggers a PVC provisioning or cleanup operation, causing the local-path-provisioner to load the modified helperPod.yaml template.
5. The local-path-provisioner creates a HelperPod based on the attacker-controlled template.
6. The malicious HelperPod is deployed on a node within the cluster, inheriting the injected privileges, such as privileged access or a host root filesystem mount.
7. The attacker leverages the privileged HelperPod to access sensitive host files, read ServiceAccount tokens, or modify files on the host node.
8. The attacker escalates privileges and potentially compromises the entire node or cluster.

Impact

Successful exploitation allows attackers to gain unauthorized access to sensitive host files, including ServiceAccount tokens from other pods residing on the same node. Attackers can also access other tenants’ local-path volume data, potentially leading to data breaches and further lateral movement within the cluster. Modification of files on the host node can disrupt services and compromise the integrity of the system. The vulnerability, CVE-2026-44543, presents a significant risk to Kubernetes environments utilizing the Rancher local-path-provisioner.

Recommendation

• Upgrade to local-path-provisioner version v0.0.34 or later to incorporate the fix that validates the HelperPod template, mitigating the risk of injecting malicious configurations (reference: Patches section).
• Restrict write access to the local-path-config ConfigMap in the local-path-storage namespace, ensuring that only trusted administrators can modify this ConfigMap (reference: Workarounds section).
• Mark the ConfigMap as immutable after deployment to prevent unauthorized modifications (reference: Workarounds section and example kubectl command).
• Enable Kubernetes Pod Security Admission (PSA) for the local-path-storage namespace, enforcing a security policy like baseline to prevent privileged HelperPods from being created, even if the template is altered (reference: Workarounds section and example kubectl command).
• Monitor Kubernetes audit logs for modifications to the local-path-config ConfigMap in the local-path-storage namespace, alerting on unexpected changes.