# CVE-2026-130623: Incorrect authorization in the credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-is


- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026

## What is CVE-2026-130623?

CVE-2026-130623 is a medium-severity vulnerability in aws-privateca-issuer, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-130623?


## How do I fix CVE-2026-130623?

No fix has been published for CVE-2026-130623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130623 being exploited?

There is no known exploitation of CVE-2026-130623 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130623 and fix it if it is affected.

What it is: CVE-2026-130623 is a medium-severity vulnerability in aws-privateca-issuer, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130623 in the wild and no public exploit code.

Affected product: aws-privateca-issuer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130623/ (Markdown: https://insights.sbomify.com/CVE-2026-130623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130623
- OSV: https://osv.dev/vulnerability/CVE-2026-130623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130623/
Summaries are generated and may contain mistakes; the official description above is the record.
