CVE-2026-130623: Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
Incorrect authorization in the credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, from every AWS Private CA and certificate template reachable by the controller's own AWS identity or by any IAM role that identity can assume. This happens because a namespace-scoped issuer that supplies no credentials, or sets only a role, falls back to the controller's own identity.
To remediate this issue, users should first update any namespace-scoped issuers that rely on the controller's identity to use their own credentials. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
aws-privateca-issuerto a version that resolves this vulnerability.Fixed in 1.12.0 - Upgrade
Upgrade
AWS Private CA Connector for Kubernetes EKS add-onto a version that resolves this vulnerability.Fixed in v1.12.0-eksbuild.1 - Configuration
Update namespace-scoped issuers that rely on the controller's identity to use their own credentials.
namespace-scoped issuers credentials = issuer's own credentials
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated remote user needs permission to create namespace-scoped issuers. Exploitation is relevant when the created issuer supplies no credentials or specifies only a role, causing it to fall back to the controller identity.
What resources could an attacker access through the affected controller identity?
The attacker may obtain certificates, including subordinate CA certificates, from every AWS Private CA and certificate template reachable by the controller's AWS identity or by IAM roles that identity can assume.
What should be done before upgrading?
First update namespace-scoped issuers that rely on the controller identity so they use their own credentials. Then upgrade aws-privateca-issuer to version 1.12.0, or upgrade the EKS add-on to v1.12.0-eksbuild.1.