Bug 2552475 (CVE-2026-77524) - CVE-2026-77524 github.com/kedacore/keda: KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication
Summary: CVE-2026-77524 github.com/kedacore/keda: KEDA: Privilege escalation from name...
Keywords:
Status: NEW
Alias: CVE-2026-77524
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-14 17:06 UTC by OSIDB Bzimport
Modified: 2026-10-16 10:55 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.