CVE-2026-6437: AWS EFS CSI Driver Mount Option Injection

Published Apr 17, 2026
·
Updated

Summary The Amazon EFS CSI Driver is a Container Storage Interface driver that allows Kubernetes clusters to use Amazon Elastic File System. An issue exists where, under certain circumstances, unsanitized values in the volumeHandle and mounttargetip fields are passed directly to the mount command, allowing injection of arbitrary mount options.

Impact An actor with PersistentVolume creation privileges can inject arbitrary mount options by appending comma-separated values to the Access Point ID in volumeHandle or to the mounttargetip volumeAttribute. The mount utility parses comma-separated values as separate options, causing the injected options to be applied to the filesystem mount without authorization.

Impacted versions: <= v3.0.0

Patches This issue has been addressed in Amazon EFS CSI Driver version v3.0.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds Restrict PersistentVolume and StorageClass creation to cluster administrators using Kubernetes RBAC, preventing untrusted users from supplying arbitrary field values.

References If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Acknowledgement We would like to thank Shaul Ben-Hai from Sentinel One for collaborating on this issue through the coordinated vulnerability disclosure process.

Other sources

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

MITRE

Affected Software

3 affected componentsFixes available
Amazon Web Services AWS EFS CSI Driver<3.0.1
go/github.com/kubernetes-sigs/aws-efs-csi-driver<1.7.8-0.20260416142831-51806c22c575
1.7.8-0.20260416142831-51806c22c575
Amazon Efs Csi Driver Kubernetes<3.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/kubernetes-sigs/aws-efs-csi-driver to a version that resolves this vulnerability.

    Fixed in 1.7.8-0.20260416142831-51806c22c575
  2. Upgrade

    Upgrade aws-efs-csi-driver to a version that resolves this vulnerability.

    Fixed in v3.0.1
  3. Compensating control

    Restrict PersistentVolume and StorageClass creation to cluster administrators using Kubernetes RBAC, preventing untrusted users from supplying arbitrary field values.

Event History

Apr 17, 2026
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
Affected Software
Apr 18, 2026
Advisory Published
via GitHub·01:07 AM
Data Sourced
via GitHub·01:07 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-6437?

CVE-2026-6437 is considered a high severity vulnerability due to the potential for remote authenticated users to inject arbitrary mount options.

2

How do I fix CVE-2026-6437?

To fix CVE-2026-6437, upgrade the AWS EFS CSI Driver to version 3.0.1 or later.

3

Who is affected by CVE-2026-6437?

CVE-2026-6437 affects users with PersistentVolume creation permissions using AWS EFS CSI Driver versions prior to 3.0.1.

4

What types of attacks are possible with CVE-2026-6437?

CVE-2026-6437 may allow attackers to manipulate volume mount options potentially leading to privilege escalation or system instability.

5

Is there a workaround for CVE-2026-6437 before upgrading?

A recommended workaround for CVE-2026-6437 is to restrict PersistentVolume creation permissions to trusted users until an upgrade can be conducted.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203