NetSight
high7.1

CVE-2026-130622

Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenti…

Impact

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.

An attacker can exploit this over the network, with a regular user account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data being read, high risk of data or systems being changed. The attack can reach beyond the vulnerable component itself.

Affected products · AWS

ProductAffected versions
Aws-privateca-issuer
before 1.12.0
before 1.12.0-eksbuild.1

Weakness classification

References