Vulnerabilities

AWS Patches CVE-2026-119115 Kubernetes Certificate Flaw in Private CA Connector

A flaw in AWS Private CA Connector for Kubernetes let users exceed certificate-issuing permissions. Check request configs before you update.

AWS Patches CVE-2026-119115 Kubernetes Certificate Flaw in Private CA Connector

On October 29, AWS disclosed CVE-2026-119115 in AWS Private CA Connector for Kubernetes. Under certain conditions, an authenticated user could get a certificate from an issuer they weren’t authorized to use. Patches are available, but you need to check your configuration before you deploy them.

What the vulnerability allows

The aws-privateca-issuer component connects cert-manager to AWS Private Certificate Authority. The bug is in how it tells a namespace-scoped issuer apart from a cluster-wide issuer. A policy that allowed only the namespace-scoped issuer might not have stopped the cluster-wide issuer from issuing a certificate.

AWS says users could also obtain subordinate certificate authority certificates. That makes this a problem with trust boundaries and permissions across the environment. The advisory doesn’t say whether the vulnerability is being actively exploited.

Who needs to update

Vulnerable versions are aws-privateca-issuer releases earlier than 1.10.1 and Amazon EKS add-on releases earlier than 1.10.1-eksbuild.1. Administrators should find out how the component was installed and which version is actually running in the cluster.

The fix adds stricter validation of the issuerRef.kind field. If that value is wrong or missing, certificate renewal can stop. You may not see the effect until the current certificate expires, so a successful restart of the component doesn’t prove the update worked.

What to do now

  • Review CertificateRequest and Certificate resources, as well as Ingress annotations.
  • Set the correct issuer kind: AWSPCAIssuer or AWSPCAClusterIssuer.
  • Deploy the patched version and confirm that certificates are issued and renewed correctly.
  • If the update has to wait, restrict approval policies and RBAC rules by both issuer name and issuer kind.

SecurHUB’s take

Certificate controls should also cover the permissions of the applications that request certificates. A security audit is a good time to review access boundaries between namespaces and to find out which services depend on automatic certificate renewal.

Sources: AWS, SecurityVulnerability.io

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk