Skip to content
TrustList
Security advisories

AWS bulletins fix efs-utils port race and Private CA Connector authorisation flaws

Editorial

By TrustList Editorial

Bulletin 2026-186 covers amazon-efs-utils before 3.3.5; 2026-187 covers aws-privateca-issuer before 1.12.0, which stops cross-namespace credential use and so needs issuers migrated before upgrading.

About AWS bulletins fix efs-utils port race and Private CA Connector authorisation flaws

AWS bulletins fix efs-utils port race and Private CA Connector authorisation flaws

17 November 2026: AWS has published two security bulletins, both rated Important (requires attention). Bulletin 2026-186-AWS covers a race condition in amazon-efs-utils, and 2026-187-AWS covers two authorisation flaws in the AWS Private CA Connector for Kubernetes. The second one needs preparation before you upgrade.

Not yet independently verified. Neither bulletin gives a CVSS score, and neither reports exploitation in the wild; both are marked Important (requires attention). We did not test the fixes or the migration steps for the Private CA Connector. We will update this when it can be confirmed, and remove this note.

Bulletin 2026-186: a port race in efs-utils

CVE-2026-130621 is a time-of-check to time-of-use race in the way amazon-efs-utils chooses a local port. When two mounts start at the same moment on one host, they can pick the same port, so one mount can be served by the other mount's tunnel (stunnel or the proxy). AWS says the impact is limited to access between workloads on the same host at the same time. It adds that the issue grants no access beyond what the host already had, because the host owner set up every mount involved, and that it does not reveal the other mount's IAM credentials or TLS session keys.

The affected versions are amazon-efs-utils before v3.3.5 and aws-efs-csi-driver before v3.5.4, plus the Amazon EKS EFS CSI add-on before v3.5.4-eksbuild.1, because efs-utils is bundled in the driver. Upgrade to those versions or later.

AWS says no workaround fully fixes the issue, but two steps reduce the risk. Widen the local port range in /etc/amazon/efs/efs-utils.conf by raising port_range_upper_bound above the default of 21049 (the example given is 30049), keeping it below the system's ephemeral port range. For the CSI driver, set the node DaemonSet flags --max-inflight-mount-calls-opt-in=true and --max-inflight-mount-calls=1 so that each node runs one mount at a time, at the cost of slower pod start-up on nodes that mount many volumes.

Bulletin 2026-187: namespace-scoped issuers

The second bulletin describes two problems in how the controller loads AWS credentials for a namespace-scoped issuer (AWSPCAIssuer). In both, a user who is allowed to create such issuers could obtain certificates, including subordinate CA certificates, that their own permissions do not allow.

CVE-2026-130622 applies where an issuer refers to an AWS credentials Secret in a different namespace: the controller then signs with that namespace's stored keys. CVE-2026-130623 applies where an issuer supplies no credentials, or only a role: it falls back to the controller's own AWS identity, and can obtain certificates from every Private CA and template that identity, or any role it can assume, can reach.

The fix is aws-privateca-issuer v1.12.0 and the EKS add-on v1.12.0-eksbuild.1.

Do the migration before you upgrade

AWS warns that v1.12.0 rejects a cross-namespace secretRef and removes the fallback to the controller's identity, so issuers that rely on either will stop issuing once you upgrade. Record which issuers are affected first, apply the v1.12.0 custom resource definitions, and then migrate: copy any credentials Secret into the issuer's own namespace and update its reference, and give every issuer that relied on the controller's identity its own credentials, using a serviceAccountRef with IRSA or a same-namespace secretRef. AWS notes that EKS Pod Identity cannot be assigned per issuer, so those issuers should move to IRSA. To avoid an outage, keep both the controller's identity and the issuer's ServiceAccount in the role trust policy until the upgrade is done.

There is a configuration switch, enableIssuerAmbientCredentials, that restores the fallback, but AWS says it leaves the cluster exposed to CVE-2026-130623 and should be used only where everyone who can create issuers is trusted.

If you cannot upgrade yet, restrict permission to create or update AWSPCAIssuer resources to cluster administrators and review the issuers tenants have already created. Where tenants must keep that permission, there is no partial mitigation for CVE-2026-130622.

Our cloud computing category lists cloud providers and related companies.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in