GPU VulnDB

Database/Container, Kubernetes & orchestration

aws-privateca-issuer: namespace-scoped issuers fall back to the controller's own AWS identity

CVSS 5.1CVE-2026-130623Container, Kubernetes & orchestrationcurated

Impact

A namespace-scoped issuer that supplies no credentials, or sets only a role, uses the controller's own AWS identity. A user who can create such an issuer in one namespace can then get certificates, including subordinate CA certificates, from every AWS Private CA and certificate template that the controller identity can reach, or reach through any IAM role it can assume. On a multi-tenant GPU cluster where tenants own namespaces, one tenant can obtain certificates that other tenants' services or cluster infrastructure trust. A subordinate CA certificate would let them issue further certificates of their own. The flaw is in the credential handling, so the scope of exposure is set by what the controller's IAM identity is allowed to do.

Who can reach it

An authenticated Kubernetes user with RBAC permission to create namespace-scoped issuers (AWSPCAIssuer) in any namespace. Network reachability to the API server is needed; no AWS credentials of their own are needed.

What to do

Before upgrading, change every namespace-scoped issuer that relies on the controller's identity so that it supplies its own credentials. Then upgrade aws-privateca-issuer to 1.12.0, or the EKS add-on to v1.12.0-eksbuild.1. The upgrade rolls the controller pod and does not touch the nodes. Until then, restrict who can create namespace-scoped issuers and narrow the controller's IAM permissions and assumable roles. Review certificates issued from your Private CAs, especially subordinate CA certificates, for unexpected requesters.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.