AWS aws-privateca-issuer
Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes
Incorrect authorization in the issuer resolution logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before v1.10.1 might allow an authenticated remote user to obtain certificates, including subordinate CA certificates, signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize. To remediate this issue, users should upgrade aws-privateca-issuer to version v1.10.1 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.10.1-eksbuild.1, and update any certificate requests, Certificate resources, or Ingress annotations whose issuerRef.kind is missing, incorrect, or does not match the referenced issuer, since v1.10.1 requires issuerRef.kind to be exactly AWSPCAIssuer or AWSPCAClusterIssuer and to match the issuer it references.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.10.1
Fixed in 1.10.1
- < 1.10.1-eksbuild.1
Fixed in 1.10.1-eksbuild.1
Mitigation
Upgrade aws-privateca-issuer to 1.10.1 or later.
Upgrade aws-privateca-issuer to 1.10.1-eksbuild.1 or later.
References
- Patch github.com/cert-manager/aws-privateca-issuer/r…
- Vendor advisory github.com/cert-manager/aws-privateca-issuer/s…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-15…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.