dbcve.org
Efs Csi DriverApplication · Amazon

CVE-2026-6437

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-17
Fix available
A fix is available. Upgrade to 3.0.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper neutralization of argument delimiters in the volume handling component in AWS EFS CSI Driver (aws-efs-csi-driver) before v3.0.1 allows remote authenticated users with PersistentVolume creation permissions to inject arbitrary mount options via comma injection. To remediate this issue, users should upgrade to version v3.0.1

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper neutralization of argument delimiters in the volume handling component of AWS EFS CSI Driver allows authenticated users with PersistentVolume creation permissions to inject arbitrary mount options via comma injection, potentially bypassing security controls or causing unintended mount behavior.

MitigationUpgrade aws-efs-csi-driver to version v3.0.1 or later to remediate the comma injection vulnerability in mount option handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Efs Csi DriverApplication
Affected:< 3.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify EFS CSI Driver deployment version
    Run 'kubectl get deployment -n kube-system aws-efs-csi-driver -o jsonpath='{.spec.template.spec.containers[0].image}'' to retrieve the container image tag, then extract the version number from the image tag (for example, the 'v' prefix and numeric version)
    Affected if The extracted version number is lower than 3.0.1 (for example, v2.x.x or v1.x.x)
  2. Verify EFS PersistentVolume resources exist
    Run 'kubectl get pv -o json' to list all PersistentVolumes, then search for entries where 'spec.csi.driver' equals 'efs.csi.aws.com' using a JSON path query or grep for 'efs.csi.aws.com'
    Affected if Any PersistentVolume resources are using the efs.csi.aws.com driver (indicates the vulnerable component is in use)
  3. Confirm PersistentVolume creation permissions exist
    Run 'kubectl auth can-i create persistentvolumes --as=<username>' where <username> is the service account or user account being assessed, or review RBAC bindings in the cluster for roles granting 'create' permission on 'persistentvolumes' resources
    Affected if The assessed user or service account has create permissions on PersistentVolume resources in any namespace or cluster-wide

You are affected if your EFS CSI Driver version is lower than 3.0.1 AND you have PersistentVolume resources using the EFS CSI driver AND users or service accounts with PersistentVolume creation permissions exist in your cluster.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.1 or later
Fixed in 3.0.1
Interim mitigation

Upgrade aws-efs-csi-driver to version v3.0.1 or later to remediate the comma injection vulnerability in mount option handling.

Recommended fix High confidence

v3.0.1

  1. Upgrade the AWS EFS CSI Driver to version v3.0.1 or later
  2. Verify the upgrade was successful by checking the driver version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Efs Csi Driver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6437 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6437 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data