Answer in brief
CVE-2026-130621 records a Medium severity (CVSS 5.3) vulnerability in Time-of-check time-of-use race condition in the local port selection in AWS efs-utils. The current sources do not mark it as known exploited. The current feed maps AWS/amazon-efs-utils (generic), AWS/aws-efs-csi-driver (generic), AWS/aws-efs-csi-driver (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps AWS/amazon-efs-utils (generic), AWS/aws-efs-csi-driver (generic), AWS/aws-efs-csi-driver (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| AWS/amazon-efs-utilsgeneric | >=0 <3.3.5 | 3.3.5 |
| AWS/aws-efs-csi-drivergeneric | >=0 <3.5.4 | 3.5.4 |
| AWS/aws-efs-csi-drivergeneric | >=0 <3.5.4-eksbuild.1 | 3.5.4-eksbuild.1 |
Published upstream
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 17, 2026
A time-of-check time-of-use (TOCTOU) race condition in the local port selection in AWS efs-utils (amazon-efs-utils) before 3.3.5 might allow a user that can start EFS mounts on a shared host to read and write a different Amazon EFS or S3 Files file system that is mounted on that same host, under that mount's IAM identity and access point, via concurrent mount operations. Only file systems mounted on the same host at the same time can be affected. Every mount involved was configured by the owner of that host, using credentials and access points that owner controls, against file systems whose owners had already granted that host access, so the issue grants no access beyond what the host was already permitted and does not cross AWS account boundaries unless the host's owner configured a cross-account mount. The practical risk is lateral access between workloads on the same host at the same time, for example one container reading another container's file system under that container's identity. The issue does not expose the other mount's IAM credentials or TLS session keys. To remediate this issue, users should upgrade amazon-efs-utils to version 3.3.5 or later. Users of the Amazon EFS CSI Driver should upgrade to version 3.5.4 or later, and users of the Amazon EKS EFS CSI add-on should update to v3.5.4-eksbuild.1 or later.
Quoted source text, attributed separately from HOL analysis.