Incorrect authorization in issuer resolution in AWS Private CA Connector for Kubernetes
Impact
AWS Private CA Connector for Kubernetes versions before v1.10.1 may allow authenticated remote users to obtain unauthorized certificates. The weakness is incorrect authorization in issuer resolution logic. Affected versions are those less than v1.10.1.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.To remediate this issue, users should upgrade aws-privateca-issuer to version v1.10.1 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.10.1-eksbuild.1, and update any certificate requests, Certificate resources, or Ingress annotations whose issuerRef.kind is missing, incorrect, or does not match the referenced issuer, since v1.10.1 requires issuerRef.kind to be exactly AWSPCAIssuer or AWSPCAClusterIssuer and to match the issuer it references.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
AWS · AMZN
aws-privateca-issuer
1 range
AWS · AMZN
aws-privateca-issuer
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 1.10.1
custom versions
Other versions: unaffected
AWS · AMZN
aws-privateca-issuer
1 range
AWS · AMZN
aws-privateca-issuer
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 1.10.1-eksbuild.1
custom versions
Other versions: unaffected
Original source description
Incorrect authorization in the issuer resolution logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before v1.10.1 might allow an authenticated remote user to obtain certificates, including subordinate CA certificates, signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize.
To remediate this issue, users should upgrade aws-privateca-issuer to version v1.10.1 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.10.1-eksbuild.1, and update any certificate requests, Certificate resources, or Ingress annotations whose issuerRef.kind is missing, incorrect, or does not match the referenced issuer, since v1.10.1 requires issuerRef.kind to be exactly AWSPCAIssuer or AWSPCAClusterIssuer and to match the issuer it references.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-119115View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
AMZN · platform conditions
Any condition may hold
Any condition may hold
Vulnerable product
cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:*From (inclusive): 0
Before: 1.10.1
Any condition may hold
Vulnerable product
cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:*From (inclusive): 0
Before: 1.10.1-eksbuild.1
Original applicability statements
[
{
"operator": "OR",
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0",
"versionEndExcluding": "1.10.1"
}
]
},
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:aws:aws-privateca-issuer:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0",
"versionEndExcluding": "1.10.1-eksbuild.1"
}
]
}
]
}
]Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.