Skip to main content
Report · AWS Security BulletinsAbout CVE-2026-130622Published

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

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-130622· High 7.1

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

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.

References

Community reviews

Loading reviews…