Incorrect authorization in AWS Private CA Connector for Kubernetes
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
AWS Private CA Connector for Kubernetes (aws-privateca-issuer) versions before v1.10.1 and the EKS add-on before v1.10.1-eksbuild.1 are affected. Incorrect authorization (CWE-863) in the issuer resolution logic lets an authenticated remote user obtain certificates, including subordinate CA certificates, signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
Incorrect authorization in the issuer resolution logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before v1.10.1 might allow an authenticated remote user to obtain certificates, including subordinate CA certificates, signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize. To remediate this issue, users should upgrade aws-privateca-issuer to version v1.10.1 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.10.1-eksbuild.1, and update any certificate requests, Certificate resources, or Ingress annotations whose issuerRef.kind is missing, incorrect, or does not match the referenced issuer, since v1.10.1 requires issuerRef.kind to be exactly AWSPCAIssuer or AWSPCAClusterIssuer and to match the issuer it references.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade aws-privateca-issuer to v1.10.1, or the AWS Private CA Connector for Kubernetes EKS add-on to v1.10.1-eksbuild.1. Update certificate requests, Certificate resources and Ingress annotations so that issuerRef.kind is exactly AWSPCAIssuer or AWSPCAClusterIssuer and matches the issuer it references.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA aws-privateca-issuer (AWS) Fixed in 1.10.1
- Fix · CNA aws-privateca-issuer (AWS) Fixed in 1.10.1-eksbuild.1
Timeline
- 2026-10-29 Threatist record created from CVE-2026-119115
- 2026-10-31 Priority changed: MEDIUM → LOW
- 2026-11-05 CISA SSVC decision points changed
References
More AWS vulnerabilities
- TI-2026-23989 crypto: algif_aead - Revert to operating out-of-place KEVCVSS 3.1HIGH 7.8
- TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
- TI-2024-18648 Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM… CVSS 3.1CRITICAL 9.8
- TI-2024-05929 Openssh: regresshion - race condition in ssh allows rce/dos CVSS 3.1HIGH 8.1
- TI-2025-03847 Input validation issue in AWS Amplify Studio UI component properties CVSS 4.0CRITICAL 9.0
- TI-2026-11603 HTTP/2 Stream Parser Confusion Body-Inspection Bypass in Amazon CloudFront with AWS WAF CVSS 4.0HIGH 7.9
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences