Bug 2552475 (CVE-2026-77524)

Summary:	CVE-2026-77524 github.com/kedacore/keda: KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	bsquizza, cmitchel, dhanak, drosa, dsimansk, elicohen, kingland, mnovotny, sausingh
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in KEDA. An authenticated user with permission to create autoscaling resources can configure a HashiCorp Vault endpoint pointing to an attacker-controlled server without providing credentials. KEDA then forwards the operator's internal Kubernetes service account token to that endpoint during authentication. An attacker can intercept this privileged token, leading to cluster-wide privilege escalation and unauthorized access to sensitive secrets and administrative operations.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-14 17:06:11 UTC

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.