CVE-2026-119115

LOWCVSS 8.4 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-863

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

1 mentions across 1 observed day

What's happening

1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Full discourse1 post

Upwind Security MDR@UpwindMDR17h
🚨High - AWS Private CA Issuer Incorrect Authorization in issuerRef Resolution (CVE-2026-119115) AWS Private CA Connector for Kubernetes (aws-privateca-issuer) improperly authorizes issuer resolution when issuerRef.kind is missing/mismatched, letting an authenticated user request certs (incl. subordinate CA) signed by a cluster-scoped AWS Private CA issuer outside their approval policy. Workloads with strict issuerRef.kind matching are not impacted. 👉Affected: aws-privateca-issuer < 1.10.1 | Upgrade to 1.10.1
0000036
376 followersView on X

Explore more

Back to dashboard