CVE-2026-130622: medium-severity vulnerability in aws-privateca-issuer
Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.1epss 0.2%
Incorrect authorization in the credential loading logic 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, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.
To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer's namespace and update the issuer's secretRef.namespace to match. 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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:H/SA:N
Affected products
AWS · aws-privateca-issuerRelated CVEs — aws-privateca-issuer
In the same product, most dangerous first.
References
https://aws.amazon.com/security/security-bulletins/2026-187-aws/https://github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hwhttps://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj