Answer in brief
CVE-2026-130623 records a Medium severity (CVSS 5.1) vulnerability in Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer). The current sources do not mark it as known exploited. The current feed maps AWS/aws-privateca-issuer (generic), AWS/aws-privateca-issuer (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps AWS/aws-privateca-issuer (generic), AWS/aws-privateca-issuer (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| AWS/aws-privateca-issuergeneric | >=0 <1.12.0 | 1.12.0 |
| AWS/aws-privateca-issuergeneric | >=0 <1.12.0-eksbuild.1 | 1.12.0-eksbuild.1 |
Published upstream
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.