Live › vulnerability › GHSA-pv26-6q9q-5773
Go to dashboardThe Amazon EFS CSI Driver lets a user with PersistentVolume creation rights inject extra mount options through the mounttargetipmap volumeAttribute, because comma-separated values appended inside that JSON map are parsed as separate mount options. An attacker can therefore pass arbitrary mount options to the mount utility on the node.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 18:43 UTC. All times on this page are UTC.
Kubernetes clusters running the Amazon EFS CSI Driver between v3.1.0 and are exposed, and the risk is greatest where tenants or untrusted users can create PersistentVolumes or StorageClasses. Clusters on a patched driver, or where only administrators control volume creation, are less exposed. The sources do not say whether non-EFS deployments are affected.
v3.4.2No product ranges from the sources yet.
aws-efs-csi-driver image tag or Helm chart appVersion); affected versions are v3.1.0 through v3.4.2.mounttargetipmap and confirm only cluster administrators can create them.v3.5.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-103505 - Mount Option Injection in Amazon EFS CSI Driver
Bulletin ID: 2026-120-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/01/2026 08:30 AM PDT
Description:
The Amazon EFS CSI Driver is a Container Storage Interface driver that allows Kubernetes clusters to use Amazon Elastic File System. We identified CVE-2026-103505, where an actor with PersistentVolume creation privileges can inject additional mount options through the mounttargetipmap volumeAttribute. Appending comma-separated values to a value inside that JSON map causes the mount utility to parse them as separate mount options.
Impacted versions: >= v3.1.0 AND <= v3.4.2
Resolution:
This issue has been addressed in Amazon EFS CSI Driver version v3.5.0. 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:
Please email [email protected] with any security questions or concerns..
This page as .md · .json · in your agent: get_signal("GHSA-pv26-6q9q-5773")