AWS Private CA Kubernetes Fix Requires Issuer Credential Migration

P1 — VALIDATE AND UPDATEHigh · 7.1 (CVSS v3.1) for each CVEEXPLOITATION: NOT STATED

Quick Answer

Inventory namespace-scoped issuers, migrate credentials before installing 1.12.0, and audit certificate issuance for unauthorized CA or template use.

Confirm Scope And Apply The Supported Remediation

What to do now: Record AWSPCAIssuer and CertificateRequest resources, secret references, controller identities, IAM roles and who can create or update issuers. The Secret issue requires stored AWS keys in another namespace. The identity-fallback issue requires tenant issuer creation and an accessible controller identity or assumable role. Apply the 1.12.0 CRDs. Move approved Secrets into the issuer’s namespace or configure per-issuer IRSA with serviceAccountRef and token-creation permission. Keep both identities trusted during migration, then remove controller trust after upgrading. Test certificate issuance and renewal with least-privilege roles. Retain Kubernetes audit records, Private CA audit reports and CloudTrail IssueCertificate events; compare retrieved certificates with approved requests and revoke unexpected certificates.

Open the authoritative advisory

Last verified: 2026-11-18 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeAWS Private CA Connector for Kubernetes namespace-scoped issuers
Advisory2026-187-AWS / GHSA-c68x-c9v2-p9hw / GHSA-vx84-39ff-mhjj
CVEsCVE-2026-130622, CVE-2026-130623
Authoritative release date2026-11-17T20:00:00Z — AWS bulletin publication time, 12:00 PM PST; the RSS entry was issued at 20:11:26 UTC.
Authority revision dateNo separate material revision is established for this release.
Affected versionsaws-privateca-issuer before 1.12.0; the EKS add-on before 1.12.0-eksbuild.1. Cross-namespace credential Secrets and fallback to the controller’s AWS identity have different prerequisites.
Fixed versionaws-privateca-issuer 1.12.0 or EKS add-on 1.12.0-eksbuild.1, with the required CRD and issuer credential migration
CVSS base score7.1 (CVSS v3.1) for each CVE
CVSS severityHigh
Exploitation statusThe cited authorities do not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

Namespace-scoped issuers can use another namespace’s stored AWS credentials or inherit the controller’s broader identity, allowing certificate issuance beyond tenant authorization.

What To Validate Now

  1. Inventory. Record AWSPCAIssuer and CertificateRequest resources, secret references, controller identities, IAM roles and who can create or update issuers.
  2. Establish applicability. The Secret issue requires stored AWS keys in another namespace. The identity-fallback issue requires tenant issuer creation and an accessible controller identity or assumable role.
  3. Remediate. Apply the 1.12.0 CRDs. Move approved Secrets into the issuer’s namespace or configure per-issuer IRSA with serviceAccountRef and token-creation permission. Keep both identities trusted during migration, then remove controller trust after upgrading.
  4. Validate. Test certificate issuance and renewal with least-privilege roles. Retain Kubernetes audit records, Private CA audit reports and CloudTrail IssueCertificate events; compare retrieved certificates with approved requests and revoke unexpected certificates.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Existing issuers using removed behavior will stop issuing. EKS Pod Identity cannot be assigned per issuer. Enabling enableIssuerAmbientCredentials restores the vulnerable fallback. Restrict issuer administration while awaiting a complete upgrade.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.