KEDA
KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication
KEDA is a Kubernetes-based Event Driven Autoscaling component. In version 2.20.2 and earlier, a namespace administrator who can create TriggerAuthentication and ScaledObject resources can set hashiCorpVault.address to a tenant-controlled endpoint and select Kubernetes authentication without an explicit credential. KEDA then uses the operator pod's projected ServiceAccount token and sends it to that endpoint as a Vault login credential. The JWT-shape filter from the prior CVE-2025-68476 remediation accepts the operator token because its subject is a Kubernetes ServiceAccount, so the attacker can obtain the operator's cluster-wide permissions, including broad Secret reads and workload or admission-related operations. This vulnerability is fixed in 2.21.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.21.0
Fixed in 2.21.0
Mitigation
Upgrade keda to 2.21.0 or later.
References
- Vendor advisory github.com/kedacore/keda/security/advisories/G…
- Patch github.com/kedacore/keda/commit/1e21cc798dedd0…
- Release notes github.com/kedacore/keda/releases/tag/v2.21.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.