CVE-2026-130623 json
Incorrect authorization in credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)
published 14h ago modified 14h ago also GHSA-vx84-39ff-mhjj , EUVD-2026-127288
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository cert-manager/aws-privateca-issuer. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- AWS aws-privateca-issuer 1.12.0, 1.12.0-eksbuild.1
Is CVE-2026-130623 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N |
| CNA | 4.0 | 5.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 |
| CNA | 4.0 | 5.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- AWS aws-privateca-issuer
Classification
References
-
github.com
/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0
release-notes, patch
-
aws.amazon.com
/security/security-bulletins/2026-187-aws/
vendor-advisory
-
github.com
/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hw
third-party-advisory
-
github.com
/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj
third-party-advisory, advisory
Sources
- CVE List CVE-2026-130623
- NVD CVE-2026-130623
- Maintainer advisory GHSA-vx84-39ff-mhjj
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of cert-manager/aws-privateca-issuer published their own advisory on GitHub. Reviewed sources take precedence over it.