Vulnerability · Published Oct 14, 2026 · Assigned by GitHub_M

CVE-2026-77524KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication

Critical 9.9

In plain English

A critical-severity privilege mismanagement in keda from kedacore. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 49% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.9Critical
Exploit odds (30 days)0.6%top 51.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/kedacore/kedano fix listedGHSA-637c-6jxx-4rwm
Gogithub.com/kedacore/kedano fix listedGO-2026-6776
Gogithub.com/kedacore/keda/v22.21.0GHSA-637c-6jxx-4rwm
Gogithub.com/kedacore/keda/v22.21.0GO-2026-6776

Affected products (as reported)

VendorProductVersions
kedacore keda < 2.21.0

Weakness: CWE-269, CWE-918 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

References