CVE
aws-privateca-issuer cross-namespace credential access in credential loading
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 1.12.0, 1.12.0-eksbuild.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.12.0, 1.12.0-eksbuild.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Authenticated users with permission to create namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 can reach this flaw remotely over the network after logging in with low-privilege access. They can then use another namespace's stored AWS credentials to get certificates, including subordinate CA certificates, signed by that namespace's AWS Private CA.
Written by a model from the sources below. Verify against them.
Original 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.
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.12.0, 1.12.0-eksbuild.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130622 (Incorrect authorization in credential loading in AWS Private CA Connector for Kubernetes (aws-privateca-issuer)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130622 (entry last updated 2026-11-17):
Affected:
- AWS aws-privateca-issuer: fixed in 1.12.0
- AWS aws-privateca-issuer: fixed in 1.12.0-eksbuild.1
Fixed versions: 1.12.0, 1.12.0-eksbuild.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130622 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130622 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://aws.amazon.com/security/security-bulletins/2026-187-aws/
- https://github.com/cert-manager/aws-privateca-issuer/releases/tag/v1.12.0
- https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-vx84-39ff-mhjj
- https://github.com/cert-manager/aws-privateca-issuer/security/advisories/GHSA-c68x-c9v2-p9hw
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130622
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130622"}.Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- AWS aws-privateca-issuer
fixed in 1.12.0
- AWS aws-privateca-issuer
fixed in 1.12.0-eksbuild.1
Evidence 6
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130622
Is CVE-2026-130622 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-130622?
aws-privateca-issuer: before 1.12.0. aws-privateca-issuer: before 1.12.0-eksbuild.1.Source: cve.now feed data
How do I fix CVE-2026-130622?
Upgrade to a fixed version: 1.12.0, 1.12.0-eksbuild.1.Source: cve.now feed data