A namespace administrator who can create TriggerAuthentication and ScaledObject resources can specify a HashiCorp Vault address pointing to a malicious endpoint. When KEDA is configured with Kubernetes authentication and no explicit credentials, it uses the operator pod’s projected ServiceAccount token as a Vault login credential and sends it to that endpoint. The JWT‑shape filter implemented as part of the prior CVE‑2025‑68476 remediation accepts the operator token because its subject is a Kubernetes ServiceAccount, so the attacker’s request is authenticated, granting cluster‑wide permissions to the operator token. The compromised token can read secrets, create or modify workloads, and perform admission control operations, effectively elevating the attacker from namespace admin to cluster admin.

The vulnerability affects the KEDA project from kedacore. Versions 2.20.2 and earlier are impacted. The fix is included in KEDA v2.21.0 and later. Any environment running a vulnerable version should upgrade immediately.

The CVSS score of 9.9 indicates critical severity, and the EPSS score of < 1% indicates a very low but non‑zero exploitation probability. The vulnerability is not listed in the CISA KEV catalog. The likely exploitation path requires an attacker to already possess namespace‑level permissions to create TriggerAuthentication or ScaledObject objects. Once established, the attacker can redirect KEDA’s operator pod to a malicious Vault endpoint, gaining cluster‑wide RBAC privileges. The combination of high severity and only modest prerequisite permissions makes this a high‑risk issue in Kubernetes clusters that grant namespace administrators broad resource‑creation rights.