Skip to content
← FrontpageAmazon hallmark logoAmazonAnalysis

AWS fixes cross-namespace credential leaks in Private CA Connector for Kubernetes

Topographic elevation contour card for AWS fixes cross-namespace credential leaks in Private CA Connector for Kubernetes
VISUAL ARTWORK:Original editorial artwork. Third-party brand marks used under nominative fair use.

What happened.Amazon Web Services published security bulletin 2026-187-AWS for the AWS Private CA Connector for Kubernetes to fix critical authorization defects that exposed cluster certificates across namespace boundaries.

Why it matters.Enterprise Kubernetes clusters rely on cert-manager issuers to automate internal mutual TLS and identity tokens. When controller authorization permits cross-namespace credential inheritance, tenant isolation boundaries collapse completely. Platform teams operating shared EKS clusters must upgrade to patched connector releases immediately.

The technical specifications:

  • Cross-namespace secrets: Tracked as CVE-2026-130622, namespace-scoped issuers could reference credential secrets stored in foreign namespaces to sign certificates.
  • Identity fallback exposure: Tracked as CVE-2026-130623, issuers lacking explicit credentials fell back to the controller pod IAM identity to request subordinate authority certificates.
  • Multi-tenant impact: Unprivileged cluster tenants could forge cryptographic certificates for any domain accessible to the shared controller pod identity.
  • Hardened controller release: AWS patched aws-privateca-issuer in version 1.12.0 and updated the Amazon EKS add-on in version 1.12.0-eksbuild.1 to reject foreign secret references.