CVE-2026-130623
Incorrect authorization in the credential handling for …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- aws.amazon.com/security/security-bulletins/2026-187-aws/
- github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0
- github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hw
- github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj
- nvd.nist.gov/vuln/detail/CVE-2026-130623
- cve.org/CVERecord?id=CVE-2026-130623
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.