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 CVSS 4.0 · 5.1 Medium EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw is a missing authorization check in the credential handling of namespace‑scoped issuers in the AWS Private CA Connector for Kubernetes. A namespace‑scoped issuer that supplies no explicit credentials, or sets only a role, causes the controller to fall back to its own AWS identity. As a result, any authenticated Kubernetes user with permission to create or modify such issuers can request certificates—including subordinate CA certificates—from every AWS Private CA and certificate template that the controller’s AWS identity can access, effectively allowing the attacker to sign arbitrary certificates.

Affected Systems

AWS Private CA Connector for Kubernetes (aws‑privateca‑issuer) prior to version 1.12.0 is vulnerable. The issue also applies to the EKS add‑on; the fix is to use aws‑privateca‑issuer 1.12.0 or the EKS add‑on version v1.12.0‑eksbuild.1.

Risk and Exploitability

The CVSS base score is 5.1, indicating moderate severity. The EPSS score is not available and the vulnerability is not listed in CISA’s KEV catalog. Exploitation requires only an authenticated user with the ability to create or edit namespace‑scoped issuers, which is a common role. Once triggered, the attacker can obtain any certificate from every reachable AWS Private CA, potentially enabling impersonation or sub‑CA signing. Because the vulnerability is not known to be actively exploited and the probability of exploitation is unclear, the risk remains moderate but warrants prompt remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update all namespace‑scoped issuers that currently rely on the controller’s identity to include explicit credentials or roles that do not fall back to the controller identity.
  • Upgrade the aws‑privateca‑issuer package to version 1.12.0 or upgrade the EKS add‑on to version v1.12.0‑eksbuild.1.
  • Restrict Kubernetes RBAC permissions so that only trusted users can create or modify namespace‑scoped issuers.

Generated by OpenCVE AI on November 17, 2026 at 21:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
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'}

Weaknesses
  • CWE-441

    Unintended Proxy or Intermediary ('Confused Deputy')

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
AMZN
Published
Updated
Nov 17, 2026, 8:09 PM
Reserved
Nov 17, 2026, 2:03 PM
Status
Received
Published
Nov 17, 2026, 8:17 PM
Modified
Nov 17, 2026, 8:17 PM