CVE-2026-130622 Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: partial
- Technology
- KubernetesCloud Platforms
Description
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| aws-privateca-issuer | < 1.12.0; < 1.12.0-eksbuild.1 | 1.12.0, 1.12.0-eksbuild.1 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| aws-privateca-issuer | < 1.12.0 | 1.12.0 |
| aws-privateca-issuer | < 1.12.0-eksbuild.1 | 1.12.0-eksbuild.1 |
References
- aws.amazon.com vendor-advisory
- github.com patch release-notes
- github.com third-party-advisory
- github.com third-party-advisory
- ENISA EUVD EUVD-2026-127287 third-party-advisory