Incorrect authorization in the issuer resolution logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before v1.10.1 might allow…
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 require
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- AWS
- Product
- aws-privateca-issuer
- CVSS v3.1
- 8.5 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
- Weakness
- CWE-863
- Exposure class
- Developer platform, Cloud platform
- NVD status
- Received
Why it ranks 21 (Routine)
- CVSS v3.1 8.5 high
- Product class: developer platform, cloud platform
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-119115 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.