CVE-2026-130623
Last modified
CVE-2026-130623 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| AWS | aws-privateca-issuer | < 1.12.0 |
| AWS | aws-privateca-issuer | < 1.12.0-eksbuild.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-130623?
How severe is CVE-2026-130623?
How do I fix CVE-2026-130623?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-130608When using the admin area profile form to change ones profil…8.1
- CVE-2026-13061An authenticated user may be able to view session metadata b…4.3
- CVE-2026-130615Flowise through 3.1.4 contains a server-side request forgery…7.1
- CVE-2026-13062An authenticated user with write privileges on a Queryable E…6.5
- CVE-2026-130621A time-of-check time-of-use (TOCTOU) race condition in the l…8.2
- CVE-2026-130622Incorrect authorization in the credential loading logic in A…7.1
- CVE-2026-130626The core JDK HTTP client (a2a-java-sdk-http-client) applies …7.5
- CVE-2026-130627The Vert.x HTTP client transport (a2a-java-sdk-http-client-v…7.5
- CVE-2026-130628react-native-webview 13.7.0 through 17.1.0 on Windows contai…4.3
- CVE-2026-130629react-native-webview 13.8.0 through 17.1.0 contains a code i…4.7
- CVE-2026-13063An authenticated user with standard read/write privileges ca…6.5
- CVE-2026-130630GPAC 26.02.0 contains a NULL pointer dereference vulnerabili…5.5
Are you affected by CVE-2026-130623?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
