CVE-2026-130622: aws-privateca-issuer · Insecure Direct Object Reference
Affects aws-privateca-issuerSource CVE Database V5
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
Users should copy any credentials Secret intended for use by a namespace-scoped issuer 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. These steps fully remediate the vulnerability. Since a patch is available and the vendor manages the cloud service, applying these updates is the recommended action.
Description
CVE-2026-130622 is an authorization bypass vulnerability in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) versions before 1.12.0. It allows an authenticated user with permission to create namespace-scoped issuers to obtain certificates signed by another namespace's AWS Private CA using that namespace's stored AWS credentials. The issue arises from incorrect authorization in the credential loading logic. The vulnerability is fixed in version 1.12.0 and the EKS add-on version v1.12.0-eksbuild.1.
Reports on CVE-2026-130622
References
- github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0 (opens in a new tab)
- aws.amazon.com/security/security-bulletins/2026-187-aws/ (opens in a new tab)
- github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj (opens in a new tab)
- github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hw (opens in a new tab)