CVE
AWS amazon-efs-utils remote file access via TOCTOU race in port selection
Affects amazon-efs-utils before 3.3.5 and the Amazon EFS CSI Driver before 3.5.4 (EKS add-on before 3.5.4-eksbuild.1). Fixed in 3.3.5, 3.5.4 and 3.5.4-eksbuild.1.
Written by a model from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in amazon-efs-utils 3.3.5 · aws-efs-csi-driver 3.5.4, 3.5.4-eksbuild.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Two mounts start at the same time on one host amazon-efs-utils before v3.3.5 Amazon EFS CSI Driver before v3.5.4 (EKS add-on before v3.5.4-eksbuild.1)
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A race condition in AWS amazon-efs-utils and aws-efs-csi-driver lets an attacker with low-level login access reach the flaw remotely, without any user action, and read and write another EFS or S3 Files file system that is mounted on the same host at the same time, under that mount's identity. The issue grants no access beyond what the host already had, but it can let one workload reach another workload's file system on that host.
Original description
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.
Who should check
Teams running amazon-efs-utils before v3.3.5 or the Amazon EFS CSI Driver before v3.5.4 on shared hosts where several containers or users start EFS mounts.
Not fixed by: Widening the port range or serializing mounts does not fully fix it.
“an issue in the port selection in AWS efs-utils (amazon-efs-utils) before v3.3.5”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Two mounts start at the same time on one host amazon-efs-utils before v3.3.5 Amazon EFS CSI Driver before v3.5.4 (EKS add-on before v3.5.4-eksbuild.1)Upgrade to a fixed version: amazon-efs-utils 3.3.5 · aws-efs-csi-driver 3.5.4, 3.5.4-eksbuild.1.
Workaround: Widen the local port range used for mounts, or avoid starting mounts at the same time on one host.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130621 (Time-of-check time-of-use race condition in the local port selection in AWS efs-utils), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130621 (entry last updated 2026-11-17):
Affected:
- AWS amazon-efs-utils: fixed in 3.3.5
- AWS aws-efs-csi-driver: fixed in 3.5.4
- AWS aws-efs-csi-driver: fixed in 3.5.4-eksbuild.1
Fixed versions: 3.3.5, 3.5.4, 3.5.4-eksbuild.1.
Conditions (all must be true for the bug to be hit):
- Two mounts start at the same time on one host (source: https://aws.amazon.com/security/security-bulletins/2026-186-aws/)
- amazon-efs-utils before v3.3.5 (source: https://aws.amazon.com/security/security-bulletins/2026-186-aws/)
- Amazon EFS CSI Driver before v3.5.4 (EKS add-on before v3.5.4-eksbuild.1) (source: https://aws.amazon.com/security/security-bulletins/2026-186-aws/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Widen the local port range used for mounts, or avoid starting mounts at the same time on one host. (source: https://aws.amazon.com/security/security-bulletins/2026-186-aws/)
CISA KEV: CVE-2026-130621 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130621 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://aws.amazon.com/security/security-bulletins/2026-186-aws/
- https://github.com/aws/efs-utils/releases/tag/v3.3.5
- https://github.com/kubernetes-sigs/aws-efs-csi-driver/releases/tag/v3.5.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130621
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130621"}.Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- First seen by cve.now
Affected versions
- AWS amazon-efs-utils
fixed in 3.3.5
- AWS aws-efs-csi-driver
fixed in 3.5.4
- AWS aws-efs-csi-driver
fixed in 3.5.4-eksbuild.1
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130621
Is CVE-2026-130621 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When two mounts start at the same time on one host, they can select the same local port because the check for a free port and its use are not atomic. The advisory describes this as a time-of-check time-of-use race condition.Source: aws.amazon.com
Which versions are affected by CVE-2026-130621?
amazon-efs-utils: before 3.3.5. aws-efs-csi-driver: before 3.5.4. aws-efs-csi-driver: before 3.5.4-eksbuild.1.Source: cve.now feed data
Am I affected, and how do I check?
amazon-efs-utils before v3.3.5, the Amazon EFS CSI Driver before v3.5.4, and the Amazon EKS EFS CSI add-on before v3.5.4-eksbuild.1 are affected. To check a version, look at the installed amazon-efs-utils package version or the aws-efs-csi-driver image or add-on version.Source: aws.amazon.com
How do I fix CVE-2026-130621?
Upgrade amazon-efs-utils to v3.3.5, aws-efs-csi-driver to v3.5.4, or the EKS add-on to v3.5.4-eksbuild.1. Until then, the advisory suggests widening the local port range used for mounts or avoiding starting mounts at the same time on one host.Source: aws.amazon.com