Technical impact
An incorrect authorization check in the credential loading logic of AWS Private CA Connector for Kubernetes (aws-privateca-issuer) allows an authenticated user who can create namespace‑scoped issuers to obtain certificates— including subordinate CA certificates— signed by another namespace’s AWS Private CA. The user can reference a credentials Secret that resides in a different namespace, enabling issuance of certificates without the issuer namespace’s own credentials. This flaw creates a potential path to forge trust anchors within the cluster, compromising the integrity of TLS communications that depend on those certificates.
Affected Systems
Vulnerable versions are all releases of AWS Private CA Connector for Kubernetes (aws-privateca-issuer) prior to v1.12.0 and the corresponding EKS add‑on before v1.12.0-eksbuild.1. The affected product is the AWS Private CA Connector for Kubernetes, commonly deployed as a Kubernetes issuer for cert‑manager, by Amazon Web Services.
Risk and Exploitability
The CVSS score of 5.1 indicates a moderate severity. EPSS data is not available and the vulnerability is not listed in the CISA KEV catalogue. The attack requires the attacker to be an authenticated user with permission to create namespace‑scoped issuers, a privilege that is normally tightly controlled. Thus the risk is moderate but limited to environments where such role permissions are broadly granted.