
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE

🚨HIGH - aws-privateca-issuer cross-namespace Secret ref cert issuance (CVE-2026-130622) AWS Private CA Connector for Kubernetes (aws-privateca-issuer) has incorrect authz in credential-loading: a user who can create namespace-scoped Issuers can point the issuer at a credentials Secret in another namespace, causing cert requests to be signed via that namespace’s AWS Private CA creds (incl subordinate CA certs). Copying the Secret into the Issuer namespace mitigates. 👉Affected: aws-privateca-issuer < 1.12.0 | Upgrade to 1.12.0 (EKS add-on v1.12.0-eksbuild.1)