Technical impact
The flaw is a missing authorization check in the credential handling of namespace‑scoped issuers in the AWS Private CA Connector for Kubernetes. A namespace‑scoped issuer that supplies no explicit credentials, or sets only a role, causes the controller to fall back to its own AWS identity. As a result, any authenticated Kubernetes user with permission to create or modify such issuers can request certificates—including subordinate CA certificates—from every AWS Private CA and certificate template that the controller’s AWS identity can access, effectively allowing the attacker to sign arbitrary certificates.
Affected Systems
AWS Private CA Connector for Kubernetes (aws‑privateca‑issuer) prior to version 1.12.0 is vulnerable. The issue also applies to the EKS add‑on; the fix is to use aws‑privateca‑issuer 1.12.0 or the EKS add‑on version v1.12.0‑eksbuild.1.
Risk and Exploitability
The CVSS base score is 5.1, indicating moderate severity. The EPSS score is not available and the vulnerability is not listed in CISA’s KEV catalog. Exploitation requires only an authenticated user with the ability to create or edit namespace‑scoped issuers, which is a common role. Once triggered, the attacker can obtain any certificate from every reachable AWS Private CA, potentially enabling impersonation or sub‑CA signing. Because the vulnerability is not known to be actively exploited and the probability of exploitation is unclear, the risk remains moderate but warrants prompt remediation.