Description
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.
Published: 2026-11-17
Score: 5.1 Medium
EPSS: n/a
KEV: No
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No solution or workaround provided in the CVE record.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 17 Nov 2026 20:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
First Time appeared Aws
Aws aws-privateca-issuer
Weaknesses CWE-441
CWE-863
CPEs cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:*
Vendors & Products Aws
Aws aws-privateca-issuer
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N'}

cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:H/SA:N'}


Subscriptions

Aws Aws-privateca-issuer
cve-icon MITRE

Status: PUBLISHED

Assigner: AMZN

Published:

Updated: 2026-11-17T20:09:13.649Z

Reserved: 2026-11-17T14:03:22.970Z

Link: CVE-2026-130623

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-17T20:17:44.777

Modified: 2026-11-17T20:17:44.777

Link: CVE-2026-130623

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses