Vulnerability in github.com/rancher/local-path-provisioner (CVE-2026-44543)
Summary
Vulnerability in github.com/rancher/local-path-provisioner (CVE-2026-44543). Confidential information can be exposed externally. Exploitable via helperPod.yaml. Mitigation: upgrade to 0.0.36 or later.
Original description
The description as published by the source.
Impact
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.
Example malicious HelperPod template:
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
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' local-path volume data, or modify files on the host node.
Expected Behavior:
- The HelperPod template should not allow privileged co…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44543 has been found in github.com/rancher/local-path-provisioner.
Attackers can target a specific entry point like helperPod.yaml over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade github.com/rancher/local-path-provisioner to 0.0.36 or later.
If unsure, ask your IT team or search "github.com/rancher/local-path-provisioner CVE-2026-44543" on the vendor's site.
CVE-2026-44543 (github.com/rancher/local-path-provisioner) — CWE-1336 / CVSS v3 8.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: helperPod.yaml / securityContext.privileged / hostPath / baseline
Patched: 0.0.36 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1336) exists in github.com/rancher/local-path-provisioner. Attackers reach the vulnerable code path via helperPod.yaml.
Check the vendor advisory for the affected versions of github.com/rancher/local-path-provisioner. Attack surface: helperPod.yaml / securityContext.privileged / hostPath / baseline.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 0.0.36.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/rancher/local-path-provisioner' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/rancher/local-path-provisioner' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/rancher/local-path-provisionerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/rancher/local-path-provisioner to 0.0.36ステージング環境で 0.0.36 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com