// Security Advisory Triage
CVE-2026-119115 - Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes
AWS security bulletins · published 2026-10-31 05:46 UTC
WHAT CHANGEDCVE-2026-119115 - Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes. Source event: 2026-10-29T16:45:45+00:00. RSS discovery: 2026-10-29T18:29:07.971104+00:00.
WHY IT MATTERSCurrent bulletin, captured 2026-10-31T05:46:16.774Z:
AWS Private CA Connector for Kubernetes (aws-privateca-issuer) is an external issuer for cert-manager that signs certificate requests using AWS Private Certificate Authority. We are aware of CVE-2026-119115, an incorrect authorization issue in the issuer resolution logic. In affected versions, under certain conditions, an authenticated user whose approval policy only authorizes a namespace-scoped issuer could obtain certificates, including subordinate CA certificates, signed by a cluster-scoped issuer they are not authorized to use.
Impacted versions:
aws-privateca-issuer before v1.10.1;
AWS Private CA Connector for Kubernetes EKS add-on before v1.10.1-eksbuild.1
WHAT TO DOCurrent vendor guidance, captured 2026-10-31T05:46:16.774Z (separate from RSS discovery 2026-10-29T18:29:07.971104+00:00):
Resolution [B1]: This issue has been addressed in aws-privateca-issuer version v1.10.1 and the AWS Private CA Connector for Kubernetes EKS add-on version v1.10.1-eksbuild.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Resolution [B2]: Action required before upgrading: v1.10.1 enforces that issuerRef.kind is exactly AWSPCAIssuer or AWSPCAClusterIssuer and matches the kind of the issuer it references. Certificate requests that relied on the previous lenient resolution will stop renewing after the upgrade, and the services depending on them will be affected when those certificates expire. A missing or incorrect issuerRef.kind — including kind: Issuer, which cert-manager sets for Ingress annotations that do not specify an issuer kind — is now marked Failed; a request with kind: AWSPCAIssuer that references a cluster-scoped issuer now remains Pending indefinitely. Before upgrading, audit your CertificateRequest, Certificate, and Ingress resources and set issuerRef.kind explicitly to match the referenced issuer (AWSPCAIssuer for namespace-scoped, AWSPCAClusterIssuer for cluster-scoped).
Workarounds [B3]: If you cannot upgrade immediately, scope your certificate approval policies and RBAC rules to both the issuer name and the issuer kind.
Source for [B1], [B2], [B3]: https://aws.amazon.com/security/security-bulletins/2026-156-aws/
Deterministic source evidence; confidence not scored
Primary source ↗
written by advisory-evidence-v2
Show the reasoning — raw diff, triage verdict, confidence
RSS DISCOVERY DIFF
+## CVE-2026-119115 - Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes +https://aws.amazon.com/security/security-bulletins/rss/2026-156-aws/ +Thu, 29 Oct 2026 16:45:45 +0000 + +Bulletin ID: 2026-156-AWS Publication Date: 10/29/2026 09:30 AM PDT +Description: +We are aware of CVE-2026-119115, an incorrect authorization issue in the issuer resolution logic. In affected versions, under certain conditions, an authenticated user whose approval policy only authorizes a namespace-scoped issuer could obtain certificates, including subordinate CA certificates, signed by a cluster-scoped issuer they are not authorized to use. +Impacted versions: - aws-privateca-issuer before v1.10.1 - AWS Private CA Connector for Kubernetes EKS add-on before v1.10.1-eksbuild.1 +Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin. +Read this article
SEPARATE BULLETIN CAPTURE · complete
Retrieved separately from the RSS discovery; this does not establish historical page content.
| retrieval attempted | 2026-10-31T05:46:16.446Z |
|---|---|
| captured at | 2026-10-31T05:46:16.774Z |
| source | https://aws.amazon.com/security/security-bulletins/2026-156-aws/ |
| content SHA-256 | ba8bb82e2afd5502725d7e6d25a6552707a7f38d2d8c152976684a8d3a088e12 |
CVE-2026-119115 - Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes Bulletin ID: 2026-156-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/29/2026 09:30 AM PDT Description: AWS Private CA Connector for Kubernetes (aws-privateca-issuer) is an external issuer for cert-manager that signs certificate requests using AWS Private Certificate Authority. We are aware of CVE-2026-119115, an incorrect authorization issue in the issuer resolution logic. In affected versions, under certain conditions, an authenticated user whose approval policy only authorizes a namespace-scoped issuer could obtain certificates, including subordinate CA certificates, signed by a cluster-scoped issuer they are not authorized to use. Impacted versions: aws-privateca-issuer before v1.10.1; AWS Private CA Connector for Kubernetes EKS add-on before v1.10.1-eksbuild.1 Resolution: This issue has been addressed in aws-privateca-issuer version v1.10.1 and the AWS Private CA Connector for Kubernetes EKS add-on version v1.10.1-eksbuild.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Action required before upgrading: v1.10.1 enforces that issuerRef.kind is exactly AWSPCAIssuer or AWSPCAClusterIssuer and matches the kind of the issuer it references. Certificate requests that relied on the previous lenient resolution will stop renewing after the upgrade, and the services depending on them will be affected when those certificates expire. A missing or incorrect issuerRef.kind — including kind: Issuer, which cert-manager sets for Ingress annotations that do not specify an issuer kind — is now marked Failed; a request with kind: AWSPCAIssuer that references a cluster-scoped issuer now remains Pending indefinitely. Before upgrading, audit your CertificateRequest, Certificate, and Ingress resources and set issuerRef.kind explicitly to match the referenced issuer (AWSPCAIssuer for namespace-scoped, AWSPCAClusterIssuer for cluster-scoped). Workarounds: If you cannot upgrade immediately, scope your certificate approval policies and RBAC rules to both the issuer name and the issuer kind. References: CVE-2026-119115 GHSA-hjrh-q6pg-mh829 Please email aws-security@amazon.com with any security questions or concerns.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | Authorization bypass in Kubernetes identity/PKI component affecting EKS managed service. Privilege escalation from namespace to cluster scope. |
| signals | authorization bypass in Kubernetes issuer resolution · authenticated user can escalate from namespace-scoped to cluster-scoped issuer · affects AWS Private CA Connector for Kubernetes — managed service control plane component · affects EKS add-on — customer cannot patch without vendor fix · certificate issuance privilege escalation · fixed versions identified (v1.10.1) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | advisory-evidence-v2 ($0.00000) |