> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# AWS Private CA Connector for Kubernetes 1.12.0 fixes cross-namespace certificate issuance
- URL: https://ping2prompt.com/aws-private-ca-connector-for-kubernetes-1120-fixes-cross-namespace-certificate-i/
- Published: 2026-11-17T22:11:18.000Z
- Updated: 2026-11-17T22:11:18.000Z
- Description: aws-privateca-issuer 1.12.0 fixes CVE-2026-130622 and CVE-2026-130623, which might let users who create namespace-scoped issuers get certificates from another namespace's private CA or the controller's reachable CAs. Update to 1.12.0 after adjusting issuer secrets and credentials.
- Author: Ping2Prompt Newsroom
- Tags: Kubernetes, Vulnerabilities, Medium, #auto, #short-ping

## Two authorization flaws fixed in aws-privateca-issuer 1.12.0

aws-privateca-issuer 1.12.0 fixes two authorization flaws in the AWS Private CA Connector for Kubernetes, both in how credentials are handled for namespace-scoped issuers. Each scores 5.1 (CVSS 4.0, medium).

## Cross-namespace certificates through stored credentials

CVE-2026-130622 affects the connector's credential loading logic. A user who can create namespace-scoped issuers might get certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA. The attacker points an issuer at a credentials Secret in the other namespace, and the connector uses the AWS credentials stored there. The attack runs over the network and needs only low privileges: an authenticated user with permission to create such issuers.

## Issuers without credentials borrow the controller's identity

CVE-2026-130623 covers issuers that supply no credentials, or set only a role. Those issuers fall back to the controller's own AWS identity. A user who can create namespace-scoped issuers might then obtain certificates, including subordinate CA certificates, from any private CA and certificate template that identity can reach, or that any role it can assume can reach.

## Versions before 1.12.0 are affected

Both CVEs affect aws-privateca-issuer before 1.12.0\. You are exposed if you run it and let users create namespace-scoped issuers. The exploitation status is unknown: the sources do not say whether either flaw is being exploited.

## Update to 1.12.0 after fixing issuers and secrets

Update to aws-privateca-issuer 1.12.0, or to the EKS add-on v1.12.0-eksbuild.1 if you use the add-on. Adjust your configuration before you upgrade.

- **Secrets (CVE-2026-130622)**: copy any credentials Secret a namespace-scoped issuer is meant to use into that issuer's namespace, then set the issuer's `secretRef.namespace` to match.
- **Controller identity (CVE-2026-130623)**: update any namespace-scoped issuer that relies on the controller's identity so it uses its own credentials.

The sources give no disclosure or patch dates.

| Product                                                        | Affected      | Fixed                                  |
| -------------------------------------------------------------- | ------------- | -------------------------------------- |
| aws-privateca-issuer (AWS Private CA Connector for Kubernetes) | before 1.12.0 | 1.12.0 (EKS add-on v1.12.0-eksbuild.1) |

## Sources

- [nvd.nist.gov/vuln/detail/CVE-2026-130622](https://nvd.nist.gov/vuln/detail/CVE-2026-130622?ref=ping2prompt.com)
- [nvd.nist.gov/vuln/detail/CVE-2026-130623](https://nvd.nist.gov/vuln/detail/CVE-2026-130623?ref=ping2prompt.com)

Image: [Photo by Growtika on Unsplash](https://unsplash.com/photos/graphical-user-interface-9cXMJHaViTM?utm%5Fsource=ping2prompt&utm%5Fmedium=referral)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).