CVE-2026-130623: Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)

Published Nov 17, 2026
·
Updated

Incorrect authorization in the credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, from every AWS Private CA and certificate template reachable by the controller's own AWS identity or by any IAM role that identity can assume. This happens because a namespace-scoped issuer that supplies no credentials, or sets only a role, falls back to the controller's own identity.

To remediate this issue, users should first update any namespace-scoped issuers that rely on the controller's identity to use their own credentials. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.

Affected Software

1 affected component
AWS AWS Private CA Connector for Kubernetes (aws-privateca-issuer)<1.12.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade aws-privateca-issuer to a version that resolves this vulnerability.

    Fixed in 1.12.0
  2. Upgrade

    Upgrade AWS Private CA Connector for Kubernetes EKS add-on to a version that resolves this vulnerability.

    Fixed in v1.12.0-eksbuild.1
  3. Configuration

    Update namespace-scoped issuers that rely on the controller's identity to use their own credentials.

    namespace-scoped issuers credentials = issuer's own credentials

Event History

Nov 17, 2026
CVE Published
via MITRE·08:07 PM
Data Sourced
via MITRE·08:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated remote user needs permission to create namespace-scoped issuers. Exploitation is relevant when the created issuer supplies no credentials or specifies only a role, causing it to fall back to the controller identity.

2

What resources could an attacker access through the affected controller identity?

The attacker may obtain certificates, including subordinate CA certificates, from every AWS Private CA and certificate template reachable by the controller's AWS identity or by IAM roles that identity can assume.

3

What should be done before upgrading?

First update namespace-scoped issuers that rely on the controller identity so they use their own credentials. Then upgrade aws-privateca-issuer to version 1.12.0, or upgrade the EKS add-on to v1.12.0-eksbuild.1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203