CVE-2026-130622
Received Received - Intake

Incorrect Authorization in AWS Private CA Connector for Kubernetes

Vulnerability report for CVE-2026-130622, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: AMZN

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
AWS aws-privateca-issuer From 0 (inc) to 1.12.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-441 The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves incorrect authorization in the credential loading logic of AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before version 1.12.0. An authenticated remote user with permission to create namespace-scoped issuers could exploit it to obtain certificates signed by another namespace's AWS Private CA using that namespace's stored AWS credentials. This occurs via a namespace-scoped issuer referencing a credentials Secret in a different namespace.

Impact Analysis

This vulnerability could allow unauthorized access to certificates signed by AWS Private CA, including subordinate CA certificates. If exploited, it may lead to data breaches, unauthorized access to sensitive systems, or misuse of AWS Private CA resources. Organizations using affected versions should upgrade immediately to mitigate risks.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by potentially exposing sensitive data through unauthorized certificate issuance. GDPR requires protecting personal data, while HIPAA mandates safeguarding health information. Exploitation may lead to violations, fines, or legal consequences due to unauthorized access or data breaches.

Mitigation Strategies

Copy credentials Secrets intended for namespace-scoped issuers into the issuer's namespace and update secretRef.namespace to match. Then upgrade aws-privateca-issuer to version 1.12.0 or AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130622. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...