Skip to main content
VulnerabilityPublished

CVE-2026-130623: aws-privateca-issuer · Incorrect Authorization

Affects aws-privateca-issuerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.12.0 soon.

Data as of 17 Nov 2026, 20:22 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (AMZN)CVSS 3.17.1
CNA (AMZN)CVSS 4.05.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
AWSaws-privateca-issuerAffected
  • <1.12.0
Fixed in
  • 1.12.0
AWSaws-privateca-issuerAffected
  • <1.12.0-eksbuild.1
Fixed in
  • 1.12.0-eksbuild.1

AI-suggested

A fix is available in aws-privateca-issuer version 1.12.0 and the AWS Private CA Connector for Kubernetes EKS add-on version v1.12.0-eksbuild.1. Users should first update any namespace-scoped issuers that rely on the controller's identity to use their own credentials. Then, upgrade to the fixed versions to fully remediate the vulnerability.

Description

CVE-2026-130623 is an incorrect authorization 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, including subordinate CA certificates, from all AWS Private CAs and certificate templates accessible by the controller's AWS identity or any IAM role it can assume. This occurs because namespace-scoped issuers that do not supply credentials or only set a role default to the controller's identity. The issue is fixed in version 1.12.0 and the EKS add-on version v1.12.0-eksbuild.1.

References

Community reviews

Loading reviews…