CVE-2026-130622: Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
Incorrect authorization in the credential loading logic 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, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.
To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer's namespace and update the issuer's secretRef.namespace to match. 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
Copy the credentials Secret the namespace-scoped issuer will use into that issuer's namespace, then set secretRef.namespace to match.
AWS Private CA Connector for Kubernetes secretRef.namespace = the issuer's namespace
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated remote user needs permission to create namespace-scoped issuers. Exploitation also depends on being able to configure an issuer that references a credentials Secret in another namespace.
What can an attacker obtain if exploitation succeeds?
The attacker may obtain certificates signed by another namespace's AWS Private CA using that namespace's stored AWS credentials. This can include subordinate CA certificates.
Are all deployments affected by default?
The issue affects aws-privateca-issuer versions before 1.12.0. The described attack path requires namespace-scoped issuers and cross-namespace references to credentials Secrets; deployments without those conditions are not described as exposed.
What should be done before upgrading?
Copy each credentials Secret intended for a namespace-scoped issuer into that issuer's own namespace, then update the issuer's secretRef.namespace to match. Afterward, upgrade aws-privateca-issuer to 1.12.0 or the EKS add-on to v1.12.0-eksbuild.1.