NFS CSI driver for Kubernetes is Vulnerable to Path Traversal through Volume Identifier Parameter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

EPSS

• CVE-2026-3864: 0.73% estimated exploitation activity in the next 30 days; percentile 54.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was discovered in the Kubernetes CSI Driver for NFS where the subDir parameter in volume identifiers was insufficiently validated. Attackers with the ability to create PersistentVolumes referencing the NFS CSI driver could craft volume identifiers containing path traversal sequences (../). During volume deletion or cleanup operations, the driver could operate on unintended directories outside the intended managed path within the NFS export. This may lead to deletion or modification of directories on the NFS server.

Published by the source

21 Mar 2026, 00:31 UTC

Last modified by the source

24 Mar 2026, 16:11 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2mjq-54qg-7w6j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-3864

Advisory: NFS CSI driver for Kubernetes is Vulnerable to Path Traversal through Volume Identifier Parameter
IDs: CVE-2026-3864, GHSA-2mjq-54qg-7w6j
Record: https://patchnext.com/advisories/cve-2026-3864 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/kubernetes-csi/csi-driver-nfs 0.0.0-20260210055231-316af2d86b91. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kubernetes-csi/csi-driver-nfs: affected < 0.0.0-20260210055231-316af2d86b91; fixed in 0.0.0-20260210055231-316af2d86b91

## Suggested inspection (read-only)
- Go github.com/kubernetes-csi/csi-driver-nfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kubernetes-csi/csi-driver-nfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2mjq-54qg-7w6j (GitHub-reviewed advisory GHSA-2mjq-54qg-7w6j lists affected ranges: Go github.com/kubernetes-csi/csi-driver-nfs >=0 <0.0.0-20260210055231-316af2d86b91)

Commands are suggestions: review each one before running it.