CVE-2026-130622 and CVE-2026-130623 - Incorrect authorization in credential loading and handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
Bulletin ID: 2026-187-AWS
Scope: AWS
Content Type: Important (requires attention)
Publication Date: 11/17/2026 12:00 PM PST
Description:
AWS Private CA Connector for Kubernetes (aws-privateca-issuer) is an open-source controller, maintained by AWS and distributed as an Amazon EKS add-on, that issues certificates from AWS Private CA for cert-manager.
We identified two issues in how the controller loads AWS credentials for a namespace-scoped issuer (AWSPCAIssuer). In both, a user with permission to create namespace-scoped issuers could obtain certificates, including subordinate CA certificates, that their own permissions do not authorize.
- CVE-2026-130622: a namespace-scoped issuer that references an AWS credentials Secret in a different namespace causes the controller to sign with that namespace's stored AWS credentials. This applies only where a namespace stores AWS access keys in a Kubernetes Secret.
- CVE-2026-130623: a namespace-scoped issuer that supplies no credentials, or sets only a role, falls back to the controller's own AWS identity. Such an issuer can obtain certificates from every AWS Private CA and certificate template reachable by that identity or by any IAM role the identity can assume. This applies wherever the controller uses its own AWS identity (IRSA, EKS Pod Identity, EC2 Instance Role, or IAM Roles Anywhere) and tenants can create namespace-scoped issuers
Impacted versions:
- aws-privateca-issuer before v1.12.0
- AWS Private CA Connector for Kubernetes EKS add-on before v1.12.0-eksbuild.1
Resolution:
These issues have been addressed in aws-privateca-issuer version v1.12.0 and the AWS Private CA Connector for Kubernetes EKS add-on version v1.12.0-eksbuild.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Action required before upgrading: v1.12.0 rejects a cross-namespace secretRef and no longer lets a namespace-scoped issuer fall back to the controller's AWS identity, so issuers that rely on either will stop issuing after the upgrade. Before upgrading, record which issuers are affected. Then apply the v1.12.0 CRDs (EKS add-on users can apply them directly before updating the add-on) and migrate those issuers as follows.
For CVE-2026-130622, copy any credentials Secret you intend a namespace-scoped issuer to use into that issuer's namespace, and update the issuer's secretRef.namespace to match.
For CVE-2026-130623, give every namespace-scoped issuer that relies on the controller's AWS identity its own credentials, including an issuer that sets only a role. Use either a serviceAccountRef with IRSA or a same-namespace secretRef. A serviceAccountRef needs IRSA set up for the issuer's ServiceAccount, and the controller needs permission to create tokens for that ServiceAccount. To prevent outages, ensure both the controller's identity and the ServiceAccount are in the trust policy of each issuer's IAM role until the upgrade is complete. Remove the controller's entry after upgrading. Issuers using the controller's EKS Pod Identity credentials should move to IRSA since EKS Pod Identity cannot be assigned per issuer.
Setting the Helm chart or EKS add-on configuration value enableIssuerAmbientCredentials to true restores the fallback to the controller's AWS identity, but leaves the cluster exposed to CVE-2026-130623. Use it only where everyone who can create a namespace-scoped issuer is trusted.
To identify certificates that may have been issued incorrectly, review the issuers you recorded, your AWSPCAIssuer and CertificateRequest resources, and Kubernetes API audit logs (if enabled). CertificateRequest resources may have been deleted. Then generate an AWS Private CA audit report (CreateCertificateAuthorityAuditReport) or review AWS CloudTrail IssueCertificate events, retrieve each certificate by its ARN with GetCertificate, and compare it against the certificates expected in each cluster. Revoke any unexpected certificate with RevokeCertificate.
Workarounds:
If you cannot upgrade immediately, restrict permission to create or update AWSPCAIssuer resources to cluster administrators, and review any existing AWSPCAIssuers created by tenants. This will mitigate both issues until you can upgrade. If tenants must keep permission to create or update AWSPCAIssuer resources, there is no partial mitigation for CVE-2026-130622. You can reduce the risk of CVE-2026-130623 by scoping the controller's AWS identity to only the certificate authorities, templates and roles that every principal allowed to create issuers may use. Upgrading is the only complete remediation.
References:
Please email aws-security@amazon.com with any s ecurity questions or concerns.