CVE-2026-130622

7.1High

Published 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.1CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
High
Privileges
Low
User action
None
Impact
High impact on integrity
Weakness
CWE-441, CWE-639

What an attacker gets

Authenticated users with namespace-scoped issuer permissions can obtain unauthorized certificates, including subordinate CA certificates. This requires the attacker to have existing access to create namespace-scoped issuers.

Root cause

The credential loading logic incorrectly authorizes access to AWS credentials stored in other namespaces.

Affected versions

aws-privateca-issuer before 1.12.0

CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N

Fix & remediation

Copy credential Secrets into the issuer's namespace and update secretRef.namespace, then upgrade to aws-privateca-issuer 1.12.0 or EKS add-on v1.12.0-eksbuild.1.

remediation — bash
$ helm upgrade aws-privateca-issuer aws-privateca-issuer/aws-privateca-issuer --version 1.12.0

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-130622