{"schema":"vulnpedia.research/1","cve":"CVE-2026-130622","references":[{"url":"https://aws.amazon.com/security/security-bulletins/2026-187-aws/","tags":["vendor-advisory"],"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","origins":[{"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","tags":["vendor-advisory"],"url":"https://aws.amazon.com/security/security-bulletins/2026-187-aws/"}]},{"url":"https://github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0","tags":["patch","release-notes"],"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","origins":[{"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","tags":["patch","release-notes"],"url":"https://github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0"}]},{"url":"https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hw","tags":["third-party-advisory"],"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","origins":[{"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","tags":["third-party-advisory"],"url":"https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hw"}]},{"url":"https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj","tags":["third-party-advisory"],"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","origins":[{"source":"mitre","sourceId":"AMZN","modified":"2026-11-17T20:08:58.932Z","tags":["third-party-advisory"],"url":"https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[],"sourceTimes":{"primary":"2026-11-17T20:08:58.932Z","cisa-kev":"2026-11-17T21:15:20.983Z","exploitdb":"2026-11-17T21:15:20.983Z","metasploit":"2026-11-17T21:15:20.983Z","zdi":"2026-11-17T21:15:20.983Z","oss-security":"2026-11-17T21:15:20.983Z","full-disclosure":"2026-11-17T21:15:20.983Z","cert-cc":"2026-11-17T21:15:20.983Z","watchtowr":"2026-11-17T21:15:20.983Z","lexfo":"2026-11-17T21:15:20.983Z","google-security-research":"2026-11-17T21:15:20.983Z","vulncheck-initial-access":"2026-11-17T21:15:20.983Z","vulncheck-kev":"2026-11-17T21:42:38.097Z","ghsa":"2026-11-17T21:42:57.814Z","pysec":"2026-11-17T21:42:57.814Z","go":"2026-11-17T21:42:57.814Z","rustsec":"2026-11-17T21:42:57.814Z"},"sourceFields":{"schema":"vulnpedia.source-fields/1","primary":{"description":"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.\n\n\n\nTo 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.","published":"2026-11-17","cwe":[{"id":"CWE-639","name":"Authorization bypass through User-Controlled key"},{"id":"CWE-441","name":"Unintended proxy or intermediary ('confused deputy')"}],"labels":{"vendors":["AWS"],"products":["aws-privateca-issuer"]},"ssvc":null},"nvd":null},"freshness":{"checkedAt":"2026-11-17T21:52:27.493Z","changedAt":"2026-11-17T20:18:34.641Z","pocChangedAt":null,"addedPoCs":[],"removedPoCs":[],"changedPoCs":[]},"labels":{"vendors":["AWS"],"products":["aws-privateca-issuer"]},"evidence":{"version":"2026-11-17T21:52:27.493Z#730d6020ae23267ab007e18e54232a1320e66979f545e0d3183dd356c0a11d89","checkedAt":"2026-11-17T21:52:27.493Z","changedAt":"2026-11-17T20:18:34.641Z","pocChangedAt":null}}