Security / News explained
A Kubernetes namespace did not contain the certificate issuer’s AWS authority
AWS’s November 17 disclosure concerns two ways namespace-scoped certificate issuers could borrow broader AWS authority. The fixes also change issuance behavior, so migration belongs in the upgrade plan.
AWS disclosed two authorization flaws in its Private CA Connector for Kubernetes on November 17, 2026. Versions before 1.12.0 are affected; the EKS add-on fix is 1.12.0-eksbuild.1. The relevant permission is the ability to create namespace-scoped certificate issuers. [1]
For CVE-2026-130622, an issuer could reference an AWS credentials Secret in another namespace. The controller loaded those credentials without enforcing the namespace match. This path applies where AWS access keys are stored in Kubernetes Secrets. [2]
CVE-2026-130623 concerns an issuer supplying no credentials, or only a role. It could fall back to the controller’s AWS identity and reach certificate authorities, templates or assumable roles available to that identity. The possible certificates include subordinate CA certificates. [3]
Our interpretation is that the namespace label gave an incomplete picture of authority. The useful question is which AWS principal actually signs a request. A controller serving several tenants can possess privileges that an individual tenant should never acquire simply by naming an issuer.
The upgrade changes a working assumption
The 1.12.0 release is dated November 2, 2026, before the November 17 security disclosure. Its notes describe rejecting cross-namespace Secret references and removing default fallback to controller credentials for AWSPCAIssuer. They identify AWSPCAClusterIssuer as unaffected by those changes. [4]
The ambient-credentials advisory calls for applying the new CRDs and migrating affected issuers to their own credentials. Options include IRSA through serviceAccountRef or a Secret in the issuer’s namespace. An issuer that previously specified only a role also needs attention. [3]
That makes continuity part of the security work. A certificate request that succeeded through an unintended fallback may stop succeeding after the fix. An upgrade rehearsal needs to establish both that legitimate requests still work and that a tenant cannot borrow another principal’s reach.
Consider a hypothetical platform with separate application teams sharing one controller. A renewal failure after tightening identity handling could look like an ordinary availability incident. The meaningful acceptance question is whether the intended team can obtain its intended certificate through an explicitly assigned identity. This is an illustrative review criterion, not a claim about a tested customer cluster.
A compatibility switch carries a security consequence
Setting enableIssuerAmbientCredentials to true restores the previous fallback behavior and leaves exposure to CVE-2026-130623. The advisory limits that option to environments where everyone able to create a namespace-scoped issuer is trusted. [3]
In our view, a switch that makes a renewal work again deserves an explicit decision record: what authority is being restored, who can invoke it and when the exception will end. Operational success and an intended authorization boundary need to be reviewed together.
Until an upgrade is possible, AWS recommends restricting creation or updates of AWSPCAIssuer resources to cluster administrators and reviewing existing tenant-created issuers. It describes upgrading as the complete remediation. The issue therefore warrants a controller and permission inventory, rather than a conclusion drawn from the cluster’s EKS version alone. [1]
The distinction matters for ownership. Platform administrators may operate the controller, application teams may own issuer definitions, and another group may own the certificate authority. A useful change plan connects those responsibilities to the same request path instead of treating them as unrelated configuration tickets.
Review what the old authority may have issued
The Secret-reference advisory also recommends reviewing issuer and CertificateRequest resources, available Kubernetes audit logs and AWS Private CA issuance evidence. Request resources may have been deleted. Its response includes comparing issued certificates with expectations and revoking unexpected certificates. [2]
Our reading is that changing future credential selection and reviewing earlier issuance answer separate questions. The version update establishes the corrected behavior going forward. The historical review investigates what the earlier permissions may have allowed. Neither task establishes, on its own, that a particular installation was exploited.
A practical response record can identify the installed connector or add-on version, the issuers that used fallback or cross-namespace references, the intended identities after migration and the outcome of authorized issuance checks. Those details make the remaining exceptions understandable to the next operator without exposing credentials.
For shared infrastructure, the durable lesson is to trace delegated work all the way to the principal performing it. A namespace can organize an issuer definition while a controller supplies much broader authority. The updated connector makes that relationship more explicit; the surrounding migration and review should do the same.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- AWS Private CA Connector for Kubernetes: CVE-2026-130622 and CVE-2026-130623AWS Security · Checked Nov 18, 2026
- Cross-namespace credentials Secret reference in AWSPCAIssuercert-manager AWS Private CA issuer maintainers · Checked Nov 18, 2026
- Namespace-scoped issuer fallback to controller AWS credentialscert-manager AWS Private CA issuer maintainers · Checked Nov 18, 2026
- AWS Private CA issuer 1.12.0 releasecert-manager AWS Private CA issuer maintainers · Checked Nov 18, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.