CVE-2026-130622
Incorrect authorization in the credential loading logic in AWS …
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.
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-130622
- cve.org/CVERecord?id=CVE-2026-130622
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.