CVE-2026-130622

Incorrect authorization in credential loading 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 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.

Analysis

AI-generated

Technical impact

An incorrect authorization check in the credential loading logic of AWS Private CA Connector for Kubernetes (aws-privateca-issuer) allows an authenticated user who can create namespace‑scoped issuers to obtain certificates— including subordinate CA certificates— signed by another namespace’s AWS Private CA. The user can reference a credentials Secret that resides in a different namespace, enabling issuance of certificates without the issuer namespace’s own credentials. This flaw creates a potential path to forge trust anchors within the cluster, compromising the integrity of TLS communications that depend on those certificates.

Affected Systems

Vulnerable versions are all releases of AWS Private CA Connector for Kubernetes (aws-privateca-issuer) prior to v1.12.0 and the corresponding EKS add‑on before v1.12.0-eksbuild.1. The affected product is the AWS Private CA Connector for Kubernetes, commonly deployed as a Kubernetes issuer for cert‑manager, by Amazon Web Services.

Risk and Exploitability

The CVSS score of 5.1 indicates a moderate severity. EPSS data is not available and the vulnerability is not listed in the CISA KEV catalogue. The attack requires the attacker to be an authenticated user with permission to create namespace‑scoped issuers, a privilege that is normally tightly controlled. Thus the risk is moderate but limited to environments where such role permissions are broadly granted.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Copy the credentials Secret intended for the namespace‑scoped issuer into that issuer’s namespace and update the issuer’s secretRef.namespace to match as a temporary workaround.
  • Upgrade aws‑privateca‑issuer to version 1.12.0 or, for the EKS add‑on, to version v1.12.0‑eksbuild.1 to apply the official fix.
  • Review and enforce RBAC policies to restrict users who can create namespace‑scoped issuers only to those who genuinely need that capability, reducing the window for exploitation.

Generated by OpenCVE AI on November 17, 2026 at 21:21 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 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.
Title Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
First Time appeared Aws
Aws aws-privateca-issuer
Weaknesses CWE-441
CWE-639
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-639

    Authorization Bypass Through User-Controlled Key

Sources

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