PoC Monitor
← All CVEs
CVE-2026-130623published 17 Nov 2026 20:07 UTCData: JSON · API

AWS aws-privateca-issuer

Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-863
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

AWS aws-privateca-issuer
  • < 1.12.0

Fixed in 1.12.0

AWS aws-privateca-issuer
  • < 1.12.0-eksbuild.1

Fixed in 1.12.0-eksbuild.1

Mitigation

Upgrade aws-privateca-issuer to 1.12.0 or later.

Upgrade aws-privateca-issuer to 1.12.0-eksbuild.1 or later.

References

1 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published17 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.