CVE-2026-130622: Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)

Published Nov 17, 2026
·
Updated

Incorrect authorization in the credential loading logic 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, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.

To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer's namespace and update the issuer's secretRef.namespace to match. 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

    Copy the credentials Secret the namespace-scoped issuer will use into that issuer's namespace, then set secretRef.namespace to match.

    AWS Private CA Connector for Kubernetes secretRef.namespace = the issuer's namespace

Event History

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

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated remote user needs permission to create namespace-scoped issuers. Exploitation also depends on being able to configure an issuer that references a credentials Secret in another namespace.

2

What can an attacker obtain if exploitation succeeds?

The attacker may obtain certificates signed by another namespace's AWS Private CA using that namespace's stored AWS credentials. This can include subordinate CA certificates.

3

Are all deployments affected by default?

The issue affects aws-privateca-issuer versions before 1.12.0. The described attack path requires namespace-scoped issuers and cross-namespace references to credentials Secrets; deployments without those conditions are not described as exposed.

4

What should be done before upgrading?

Copy each credentials Secret intended for a namespace-scoped issuer into that issuer's own namespace, then update the issuer's secretRef.namespace to match. Afterward, upgrade aws-privateca-issuer to 1.12.0 or 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