CVE-2026-77524

published 14 Oct 2026 · updated 24 Oct 2026

KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication

9.9CriticalCVSS 9.9EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
kedacore<2.21.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-77524 severity on Zeptric[![CVE-2026-77524](https://zeptric.io/badge/cve/CVE-2026-77524.svg)](https://zeptric.io/cve/CVE-2026-77524)