AWS aws-privateca-issuer
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.12.0
Fixed in 1.12.0
- < 1.12.0-eksbuild.1
Fixed in 1.12.0-eksbuild.1
Mitigation
Upgrade aws-privateca-issuer to 1.12.0 or later.
Upgrade aws-privateca-issuer to 1.12.0-eksbuild.1 or later.
References
- Patch github.com/cert-manager/aws-privateca-issuer/r…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-18…
- Vendor advisory github.com/cert-manager/aws-privateca-issuer/s…
1 more
- Vendor advisory github.com/cert-manager/aws-privateca-issuer/s…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.