GPU VulnDB

Database/Container, Kubernetes & orchestration

aws-privateca-issuer: namespace-scoped issuer can use another namespace's AWS credentials to sign certificates

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

Impact

A namespace-scoped issuer could point at a credentials Secret in a different namespace, and the connector loaded and used it. A user who may create issuers in their own namespace can therefore get certificates signed by another namespace's AWS Private CA, including subordinate CA certificates. Holding a subordinate CA certificate means they can mint certificates that the other tenant's services trust. On a multi-tenant GPU Kubernetes cluster this breaks namespace isolation for PKI.

Who can reach it

An authenticated cluster user with permission to create namespace-scoped issuers in any namespace, on a cluster where another namespace stores AWS Private CA credentials in a Secret. Network access to the Kubernetes API is required.

What to do

Before upgrading, copy every credentials Secret that a namespace-scoped issuer is meant to use into that issuer's own namespace, and set the issuer's secretRef.namespace to match. Then upgrade aws-privateca-issuer to 1.12.0, or the EKS add-on to v1.12.0-eksbuild.1. That is a controller rollout with no node impact. Review certificates issued by namespace-scoped issuers, especially subordinate CA certificates, for cross-namespace issuance.

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.