← Back
CVE-2026-44543
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.
AI summary snake-internal / snake-material-v2
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: ?/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 /
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.
❓ What is the problem
**A vulnerability** (CWE-1336) exists in github.com/rancher/local-path-provisioner. Attackers reach the vulnerable code path via ``helperPod.yaml`` without authentication.
📍 Affected scope
github.com/rancher/local-path-provisioner — . Attack surface: `helperPod.yaml` / `securityContext.privileged` / `hostPath` / `baseline`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.0.36**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/rancher/local-path-provisioner to 0.0.36ステージング環境で 0.0.36 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/rancher/local-path-provisioner
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.36"}]}]