CVE-2026-130622 and CVE-2026-130623 - Incorrect authorization in credential loading and handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
Source AWS Security Bulletins
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.1 High : upgrade to 1.12.0 soon.
Data as of 17 Nov 2026, 20:22 UTC
Thin evidence
One scorer or none| CNA (AMZN) | CVSS 3.1 | 7.1 |
|---|---|---|
| CNA (AMZN) | CVSS 4.0 | 5.1 |
- Patch
- Available – fixed in 1.12.0, 1.12.0-eksbuild.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade aws-privateca-issuer to 1.12.0; aws-privateca-issuer to 1.12.0-eksbuild.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSaws-privateca-issuer | Affected
| Fixed in
|
| AWSaws-privateca-issuer | Affected
| Fixed in
|
AI-suggested
Upgrade to AWS Private CA Connector for Kubernetes version 1.12.0 or later, or AWS Private CA Connector for Kubernetes EKS add-on version 1.12.0-eksbuild.1 or later, where this authorization issue has been fixed. No other mitigation is indicated in the advisory.
Description
AWS Private CA Connector for Kubernetes (aws-privateca-issuer) versions before 1.12.0 contain an incorrect authorization vulnerability in the credential loading logic. This flaw allows an authenticated user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA using that namespace's stored AWS credentials. This can be exploited via a namespace-scoped issuer referencing a credentials Secret in the attacker's namespace.