CVE-2026-44543: Local Path Provisioner Configuration Injection Leading to Node Compromise

Technical summary

CVE-2026-44543 is an improper validation vulnerability in Local Path Provisioner versions prior to 0.0.36. The provisioner loads the helperPod.yaml template from a ConfigMap in the local-path-storage namespace without adequate sanitization. An authenticated user with ConfigMap edit permissions can inject security-sensitive fields including securityContext.privileged, hostPath volume mounts, and Linux capabilities into the template. When PVC provisioning or cleanup operations trigger HelperPod instantiation, the provisioner deploys the attacker-controlled pod definition. The resulting pod runs with root access and host root filesystem visibility, enabling lateral movement and data exfiltration on the node.

Business impact

This vulnerability enables privilege escalation and multi-tenant data breach within Kubernetes clusters running vulnerable Local Path Provisioner versions. A malicious or compromised user account with ConfigMap permissions can persistently compromise node security, access other teams' persistent volumes, steal service account tokens for further cluster compromise, and modify host files to establish persistence. In shared or multi-tenant clusters, the risk is amplified: a single compromised developer account with appropriate RBAC permissions could expose the entire node's data and allow lateral movement to other workloads. Organizations relying on role-based access control and namespace isolation for security may find those controls bypassed.

Affected systems

SUSE Local Path Provisioner versions before 0.0.36 are affected. This provisioner is commonly deployed in Kubernetes clusters—particularly in on-premises and edge deployments—to manage local storage. Exposure depends on cluster configuration: only clusters where untrusted or insufficiently-monitored users have been granted ConfigMap edit rights in the local-path-storage namespace are at direct risk. Air-gapped or highly restricted environments may have lower exposure if RBAC policies are enforced strictly.

Exploitability

Exploitation requires legitimate authentication and RBAC permissions to edit ConfigMaps in the local-path-storage namespace. No network-based or unauthenticated exploitation path exists. However, the bar for in-cluster exploitation is low once permissions are granted: an attacker need only update a ConfigMap and then trigger a PVC operation (e.g., by creating or deleting a PersistentVolumeClaim). The attack surface widens in clusters with overly permissive RBAC policies or where service accounts are granted broad ConfigMap edit permissions. The CVSS score of 8.7 (HIGH) reflects the severity of impact once access is gained, balanced against the authentication requirement.

Remediation

Update Local Path Provisioner to version 0.0.36 or later. This version includes proper validation of the helperPod.yaml template and restricts injection of privileged fields. After patching, audit and tighten RBAC policies to limit ConfigMap edit permissions in the local-path-storage namespace to trusted administrators only. Consider using network policies and pod security policies to restrict helper pod execution contexts as a defense-in-depth measure.

Patch guidance

Verify your current Local Path Provisioner version via your Kubernetes cluster (typically visible in the provisioner deployment manifest or helm chart values). Consult SUSE's official security advisory for the exact patch delivery mechanism—this may involve a helm chart update, container image pull, or direct deployment reconfiguration depending on your installation method. Test the patch in a non-production environment first to ensure no disruption to existing PVC operations. After upgrade, confirm that the ConfigMap validation is in place by attempting to inject invalid security settings (in a lab environment) and verifying that the provisioner rejects them.

Detection guidance

Monitor audit logs for ConfigMap modifications in the local-path-storage namespace, especially changes to keys containing 'helperPod' or 'yaml'. Alert on any ConfigMap edit by unexpected users or service accounts. In running clusters, inspect active HelperPod definitions for suspicious security context settings, host path mounts, or elevated capabilities that were not present in baseline configurations. Check if any pods spawned by the provisioner are running with securityContext.privileged=true or have hostPath volumes mounted—these are strong indicators of compromise.

Why prioritize this

Although this vulnerability requires authenticated access with specific RBAC permissions, its impact is severe: node compromise, multi-tenant data exfiltration, and lateral movement into the broader cluster. In shared or multi-tenant Kubernetes environments, or clusters with delegated namespace management, the risk is elevated. Patch urgency is high for any cluster where non-administrative users have ConfigMap edit permissions, even if they are nominally 'trusted.' Organizations should prioritize patching if Local Path Provisioner is used in production storage infrastructure.

Risk score, explained

The CVSS 3.1 score of 8.7 (HIGH) reflects high impact (confidentiality, integrity, and scope change) weighted against high privileges required (PR:H). The attack vector is listed as network (AV:N) because the attacker exploits the Kubernetes API remotely, even though they must be authenticated. The low complexity (AC:L) reflects that ConfigMap modification is a straightforward operation once credentials are obtained. The lack of user interaction and cluster-wide scope (S:C) drive the severity toward the high range. This score appropriately emphasizes that while initial compromise requires credentials, the resulting node-level privilege escalation and data access are severe.

Frequently asked questions