Skip to content

CVE-2026-130623 Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)

MediumCVSS 5.1 EPSS 0.16%
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 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.

Upgrade path

1 package: 1 fixed.

PackageAffectedFixed inStatus
aws-privateca-issuer < 1.12.0; < 1.12.0-eksbuild.1 1.12.0, 1.12.0-eksbuild.1 Fixed

Affected products

ProductAffected versionsFixed in
aws-privateca-issuer < 1.12.0 1.12.0
aws-privateca-issuer < 1.12.0-eksbuild.1 1.12.0-eksbuild.1

References